agentleFS
BAKUGOS1BAKUGOS1/SkilledAgents-Toolkit/skills/codex/website-builder-setup/SKILL.md

website-builder-setup

Skill0 starsChanged 5 months agoMITView on GitHub

Install and verify the AI website builder stack: UI/UX Pro Max, Motion/Framer Motion, 21st.dev Magic, Taste, Emil Design Engineering, Impeccable, and Stitch skills.

  • Reads credentials
  • Installs packages

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 8 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user wants to set up, repair, or expand their AI website-building stack for premium marketing sites, SaaS pages, …

    line 8
  2. Distinctive:

    Do not ask for secrets in chat.

    line 25
  3. Distinctive:

    If a command fails, explain the failure briefly, provide the manual command, and continue with the rest of the stack.

    line 26
  4. Very specific:

    Prefer $CODEX_HOME\skills when CODEX_HOME is set.

    line 27
  5. Distinctive:

    After installing new Codex skills, tell the user to restart Codex so the new skills appear in the active skill list.

    line 28
  6. Very specific:

    If Node.js is missing, stop and ask the user to install the LTS version from https://nodejs.org.

    line 41
  7. Distinctive:

    If Python or Git is missing, continue where possible but tell the user which GitHub skill installs may fail.

    line 43
  8. Very specific:

    If the existing project already uses framer-motion, keep it:

    line 68
  9. Very specific:

    Always check package.json before importing either package.

    line 74
  10. Distinctive:

    Do not store or print API keys in project files.

    line 87
  11. Distinctive:

    If a destination already exists, do not overwrite it automatically.

    line 122
  12. Distinctive:

    When finished, summarize what installed, what failed if anything, and say:

    line 160

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Website Builder Setup

Use this skill when the user wants to set up, repair, or expand their AI website-building stack for premium marketing sites, SaaS pages, app mockups, motion-heavy UI, Stitch workflows, and design review loops.

What Gets Installed

Tool or skillWhat it adds
UI/UX Pro MaxDesign-system prompts, style directions, palettes, type pairings, and UI heuristics.
Motion / Framer MotionProduction animation patterns: reveals, transitions, hover/tap feedback, and reduced-motion aware effects.
21st.dev MagicComponent inspiration and generated React UI building blocks.
Taste SkillStronger visual taste rules for frontend architecture, typography, layout, color, and anti-generic UI.
Emil Design EngineeringMicro-interaction polish, animation judgment, component feel, and design-engineering review.
ImpeccableDeep UI critique, redesign, polish, UX writing, responsiveness, accessibility, and live iteration workflows.
Stitch SkillsStitch design, code-to-design, design-system extraction, prompt enhancement, and React component workflows.

Operating Style

  • Walk the user through setup in clear steps, but do the work directly when possible.
  • Do not ask for secrets in chat. If an API key is required, ask the user to set it locally or paste only when they explicitly accept that risk.
  • If a command fails, explain the failure briefly, provide the manual command, and continue with the rest of the stack.
  • Prefer $CODEX_HOME\skills when CODEX_HOME is set; otherwise use $HOME\.codex\skills.
  • After installing new Codex skills, tell the user to restart Codex so the new skills appear in the active skill list.

Step 1: Check Prerequisites

Run:

node --version
npm --version
python --version
git --version

If Node.js is missing, stop and ask the user to install the LTS version from https://nodejs.org.

If Python or Git is missing, continue where possible but tell the user which GitHub skill installs may fail.

Step 2: Install UI/UX Pro Max

Run:

npm install -g uipro-cli
uipro init --ai codex

Fallback if --ai codex is not supported:

uipro init --ai claude

Step 3: Install Motion

For Next.js or React projects, prefer the modern Motion package when starting fresh:

npm install motion

If the existing project already uses framer-motion, keep it:

npm install framer-motion

Always check package.json before importing either package.

Step 4: Connect 21st.dev Magic

The user needs a 21st.dev API key from https://21st.dev/magic/console.

For Codex plugin setup, use the available plugin workflow if present. If the user already has the key locally, the command pattern is:

$env:API_KEY="YOUR_21ST_DEV_KEY"
npx -y @21st-dev/magic@latest

Do not store or print API keys in project files.

Step 5: Install Advanced Design Skills

Resolve the built-in skill installer helper:

$codexHome = if ($env:CODEX_HOME) { $env:CODEX_HOME } else { Join-Path $HOME '.codex' }
$skillInstaller = Join-Path $codexHome 'skills\.system\skill-installer\scripts\install-skill-from-github.py'

Install the main Taste skill:

python $skillInstaller --repo Leonxlnx/taste-skill --path skills/taste-skill

Install Emil Design Engineering:

python $skillInstaller --repo emilkowalski/skills --path skills/emil-design-eng

Install Impeccable:

python $skillInstaller --repo pbakaus/impeccable --path skill --name impeccable

Install Stitch skills:

python $skillInstaller --repo google-labs-code/stitch-skills --path plugins/stitch-design/skills/code-to-design plugins/stitch-design/skills/extract-design-md plugins/stitch-design/skills/extract-static-html plugins/stitch-design/skills/generate-design plugins/stitch-design/skills/manage-design-system plugins/stitch-design/skills/upload-to-stitch plugins/stitch-build/skills/react-components plugins/stitch-build/skills/remotion plugins/stitch-build/skills/shadcn-ui plugins/stitch-utilities/skills/design-md plugins/stitch-utilities/skills/enhance-prompt plugins/stitch-utilities/skills/stitch-loop plugins/stitch-utilities/skills/taste-design

If a destination already exists, do not overwrite it automatically. Report that it is already installed.

Step 6: Optional Stitch Plugin Marketplace

For full Stitch plugin integration, add the Stitch marketplace when Codex plugin CLI is available:

codex plugin marketplace add google-labs-code/stitch-skills --ref main --sparse .agents/plugins --sparse plugins/stitch-design --sparse plugins/stitch-build --sparse plugins/stitch-utilities

Stitch workflows require the Stitch MCP server and credentials. Do not claim Stitch is fully ready until the MCP server is visible in the active tools.

Step 7: Verify

Run:

$codexHome = if ($env:CODEX_HOME) { $env:CODEX_HOME } else { Join-Path $HOME '.codex' }
Get-ChildItem (Join-Path $codexHome 'skills') -Directory | Sort-Object Name | Select-Object -ExpandProperty Name

Expected important entries:

  • taste-skill
  • emil-design-eng
  • impeccable
  • code-to-design
  • generate-design
  • manage-design-system
  • react-components
  • shadcn-ui
  • design-md
  • enhance-prompt
  • stitch-loop
  • taste-design

Done Message

When finished, summarize what installed, what failed if anything, and say:

Restart Codex to pick up the new skills.

Then the user can ask for premium website work using:

  • website-builder-setup
  • ui-ux-pro-max
  • taste-skill
  • emil-design-eng
  • impeccable
  • Stitch skills such as generate-design, stitch-loop, code-to-design, or react-components

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.