Claude-skill-registry aico-frontend-init
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/aico-frontend-init" ~/.claude/skills/majiayu000-claude-skill-registry-aico-frontend-init && rm -rf "$T"
manifest:
skills/data/aico-frontend-init/SKILL.mdsource content
Frontend Init
Initialize frontend engineer configuration files: design system and constraints.
Language Configuration
Before generating any content, check
aico.json in project root for language field to determine the output language. If not set, default to English.
Process
- Check existing: Look for
anddocs/reference/frontend/design-system.mdconstraints.md - Create directory structure:
docs/reference/frontend/ ├── design-system.md ├── constraints.md ├── designs/ └── tasks/ - Design System Setup:
- Option A: Extract from reference website using
skillaico-frontend-style-extraction - Option B: Use template from
references/design-system.template.md
- Option A: Extract from reference website using
- Constraints Setup:
- Guide user through tech stack questions
- Use template from
references/constraints.template.md
- Save output: Write to
docs/reference/frontend/
Document Header Format
All generated documents MUST use this unified header format:
# [Document Title] > Project: [project-name] > Created: YYYY-MM-DD > Last Updated: YYYY-MM-DD
Design System Options
Option A: Extract from Reference Website
If user provides a reference URL:
- Check if Playwright MCP is available
- Navigate to URL → take screenshot → analyze
- Extract design tokens using
skillaico-frontend-style-extraction
Option B: Fill Template
If no reference:
- Read template from
references/design-system.template.md - Ask about color preferences (light/dark, accent color)
- Ask about typography (serif/sans-serif)
- Fill in reasonable defaults
Constraints Questions
| Question | Options |
|---|---|
| Framework | React, Vue, Next.js, Svelte |
| TypeScript | Yes (recommended), No |
| Component Library | shadcn/ui, Ant Design, MUI, None |
| Styling | Tailwind CSS, CSS Modules, styled-components |
| Testing | Vitest, Jest, None |
| Directory Pattern | Feature-based, Type-based |
Templates
- Design tokens templatereferences/design-system.template.md
- Tech stack and conventions templatereferences/constraints.template.md
Update Instructions File
After creating constraint files, update the project's AI instructions file to reference them:
-
Check for existing instructions file:
- Look for
(Claude Code) orCLAUDE.md
(Codex) in project rootAGENTS.md - If neither exists, create
CLAUDE.md
- Look for
-
Add reference section at the end of the file:
## Reference Documents The following constraint documents should be read before starting work: - `docs/reference/frontend/design-system.md` - Design tokens and visual guidelines - `docs/reference/frontend/constraints.md` - Tech stack and coding conventions -
If file already has Reference Documents section: Append the new references if not already present
Output
✓ Created docs/reference/frontend/design-system.md ✓ Created docs/reference/frontend/constraints.md ✓ Created docs/reference/frontend/designs/ ✓ Created docs/reference/frontend/tasks/ ✓ Updated CLAUDE.md with reference to constraint files ✓ Frontend environment initialized
Key Rules
- ALWAYS use the unified header format
- MUST create both design-system.md and constraints.md
- ALWAYS create designs/ and tasks/ directories
- MUST update CLAUDE.md or AGENTS.md with reference to constraint files