Cxc Dev Frontend

Community

lidge-jun

cxc-dev-frontend

Use for frontend code and UI fixes. Triggers: CSS, responsive, animation, React, Vue, Svelte, Tailwind, redesign, anti-slop, 프론트엔드, UI 작업, 반응형, 디자인 수정.

Overview

Publisher	lidge-jun
Repository	`codexclaw`
Skill name	`cxc-dev-frontend`
Stars	51
Forks	10
Bundled files	55
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
55 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by lidge-jun on GitHub. Read the source before you install it.

Installation

Install the Cxc Dev Frontend AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/lidge-jun/codexclaw/tree/main/plugins/codexclaw/skills/dev-frontend
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/lidge-jun/codexclaw.git /tmp/codexclaw
mkdir -p .claude/skills
cp -r /tmp/codexclaw/plugins/codexclaw/skills/dev-frontend .claude/skills/cxc-dev-frontend

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cxc Dev Frontend in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cxc Dev Frontend on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cxc Dev Frontend is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Dev-Frontend — Domain-Correct Frontend Engineering

Build production-grade frontend implementations from an established product/design direction. This skill owns HTML/CSS/component/runtime implementation, responsive behavior, accessibility wiring, visual verification, and frontend platform rules.

Before selecting depth or claiming completion, read dev and its verification gate. For current/external evidence, use dev’s conditional routes.

Modular References

Condition	Reference
Every frontend change: role boundary	Role boundaries
Before designing or coding: surface defaults	Routing defaults
C2 list/detail/form screens	CRUD UI
Marketing/visual surfaces or C3+: choose topic/locale references	Core topic index
Framework implementation or configuration	Stack index
Components, direction intake, dials or objective/style classification	Design intake
Typography, color, layout, assets, icons or cutouts	Implementation
New/redesigned surfaces or visual audits	Anti-slop enforcement
Performance, accessibility, forms, state, platform or errors	Platform and runtime
WCAG 2.2 AA questions or any accessibility conformance statement	WCAG 2.2 AA
Auditing a rendered UI: violation ledger, before/after evidence, fix proof	Visual audit loop
API consumption, security UI or contract fixtures	Backend contracts
Any render/executable frontend artifact	Verification grounding
Before shipping a production frontend surface at C2+	Full pre-flight

Start with references/core/anti-slop.md, references/core/aesthetics.md, references/core/responsive-viewport.md, and references/core/visual-verification.md. Add domain/locale/stack references only when relevant. For C2 ordinary app screens (form/table/list/detail), references/core/crud-ui.md alone suffices; add the style references above for marketing/visual surfaces or C3+ work.

UI/rendering bug RCA: load dev-debugging.
Build pipeline, bundle config, or deployment: load dev-devops.
Project setup or file placement conventions: load dev-scaffolding.
Data-driven dashboards, reporting views, or data format expectations: load dev-data.

0. Frontend Routing

Before designing or coding, classify the work:

Decision	Options	Why It Matters
Product surface	landing, app, dashboard, AI tool, public service, education, game, creative	Sets density, typography scale, asset requirements
Locale	Korean-first, global/i18n, English-only	Sets CJK typography, copy, date/number formats
Density	campaign, consumer app, productivity, SaaS, ops, finance, developer console	Prevents landing-page composition inside repeated-work tools
Asset need	none, screenshot, product photo, diagram, chart, illustration, soft 3D, game asset	Prevents asset-free gradient/card UI
Soft 3D/character gate	not allowed, subtle, primary	Prevents generic cute 3D/mascot slop
Motion intensity	static, feedback-only, expressive, cinematic	Prevents cinematic motion in utility workflows

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Cxc Dev Frontend AI skill do?

Use for frontend code and UI fixes. Triggers: CSS, responsive, animation, React, Vue, Svelte, Tailwind, redesign, anti-slop, 프론트엔드, UI 작업, 반응형, 디자인 수정.

Why use Cxc Dev Frontend on TypingMind?

Because you install it once and use it with any model. Cxc Dev Frontend is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cxc Dev Frontend in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/lidge-jun/codexclaw/tree/main/plugins/codexclaw/skills/dev-frontend. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Cxc Dev Frontend?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cxc Dev Frontend?

As many as you like. As long as a model supports skills, you can use Cxc Dev Frontend with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cxc Dev Frontend AI skill free?

Yes. It is published on GitHub by lidge-jun under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Grilling

mattpocock

CommunityPopular

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Teach

Teach the user a new skill or concept, within this workspace.

Api Design

Patrones de diseño REST API incluyendo nomenclatura de recursos, códigos de estado, paginación, filtrado, respuestas de error, versionado y rate limiting para APIs de producción.

Accessibility

WCAG 2.2 レベル AA 標準を用いてインクルーシブなデジタルプロダクトを設計・実装・監査します。Web 用のセマンティック ARIA および Web・ネイティブプラットフォーム（iOS/Android）のアクセシビリティトレイトを生成するために使用します。

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Dev-Frontend — Domain-Correct Frontend Engineering

Modular References

0. Frontend Routing

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now