Figma Build
awdr74100/figwright
Build a Figma design from code or a description — the reverse of figma-codegen.
Bootstrap a fresh project of any domain -- software, book, marketing campaign, landing page, design system, or product launch.
$ npx skills add FerroxLabs/ijfw --skill ijfw-new-project -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FerroxLabs/ijfw ijfw-new-project --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/skills/ijfw-new-project .claude/skills/ijfw-new-project && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ijfw-new-project" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-new-project into .claude/skills/ijfw-new-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-new-project", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-new-projectType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FerroxLabs/ijfw --skill ijfw-new-project -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FerroxLabs/ijfw ijfw-new-project --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude/skills/ijfw-new-project .agents/skills/ijfw-new-project && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ijfw-new-project" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-new-project into .agents/skills/ijfw-new-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-new-project", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/ijfw --skill ijfw-new-project -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FerroxLabs/ijfw ijfw-new-project --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude/skills/ijfw-new-project .cursor/skills/ijfw-new-project && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ijfw-new-project" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-new-project into .cursor/skills/ijfw-new-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-new-project", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FerroxLabs/ijfw.git --path claude/skills/ijfw-new-project--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FerroxLabs/ijfw --skill ijfw-new-project -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FerroxLabs/ijfw ijfw-new-project --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude/skills/ijfw-new-project .gemini/skills/ijfw-new-project && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ijfw-new-project" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-new-project into .gemini/skills/ijfw-new-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-new-project", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FerroxLabs/ijfw ijfw-new-projectInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FerroxLabs/ijfw --skill ijfw-new-project -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude/skills/ijfw-new-project .github/skills/ijfw-new-project && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ijfw-new-project" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-new-project into .github/skills/ijfw-new-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-new-project", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/ijfw --skill ijfw-new-project -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FerroxLabs/ijfw ijfw-new-project --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/ijfw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude/skills/ijfw-new-project .opencode/skills/ijfw-new-project && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ijfw-new-project" agent skill from https://github.com/FerroxLabs/ijfw/tree/main/claude/skills/ijfw-new-project into .opencode/skills/ijfw-new-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijfw-new-project", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
ijfw-new-projectBootstrap a fresh project of any domain -- software, book, marketing campaign, landing page, design system, or product launch.
Ijfw New Project is an agent skill from FerroxLabs/ijfw. Bootstrap a fresh project of any domain -- software, book, marketing campaign, landing page, design system, or product launch. Trigger: 'new project', 'start a project', 'bootstrap project', 'init a project', 'scaffold a project', /ijfw-new-project
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files (for example `templates/book.brief.md`, `templates/campaign.brief.md` and `templates/design-system.brief.md`).
It sits in Frontend & Design, covering Project scaffolding, Landing pages and Design systems. The repository describes itself as: IJFW — It Just Fcking Works. Ferrox Labs' local-first infrastructure for AI coding agents: shared memory, smart routing, multi-AI cross-audits, disciplined workflow. The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit eda62f3. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Ijfw New Project loads about 1.4k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 605 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from FerroxLabs/ijfw at commit eda62f3, republished under its MIT licence (© FerroxLabs). 605 words, ~1,378 tokens.
.claude/skills/ijfw-new-project/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.Domain-agnostic bootstrap. Software is one domain; book, campaign, landing-page, design-system, and launch are first-class peers. The end state is the same: a confirmed brief, durable memory, and a clear next move.
Read the user's first line. Map silently:
| Phrase contains | Domain |
|---|---|
| "app", "site", "API", "service", "CLI", "library", "tool" | software |
| "book", "chapter", "manuscript", "novel", "essay collection" | book |
| "campaign", "ad", "funnel", "email sequence", "drip" | campaign |
| "landing page", "one-pager", "splash", "lead magnet" | landing-page |
| "design system", "component library", "brand kit", "tokens" | design-system |
| "launch", "release plan", "PR/FAQ", "go-to-market" | launch |
If no signal, ask once: One word: software / book / campaign / landing-page / design-system / launch?
Accept aliases. Do not interrogate. Do not assume software.
Call ijfw_memory_recall with the project name + domain. If matches return,
surface up to 3 relevant prior decisions inline:
I remember: <project> -- <decision>. Want me to apply that pattern here?
If empty, say clean slate -- no prior context and continue. Never silent.
Write .ijfw/memory/brief.md from the domain template:
software -> claude/skills/ijfw-new-project/templates/software.brief.mdbook -> claude/skills/ijfw-new-project/templates/book.brief.mdcampaign -> claude/skills/ijfw-new-project/templates/campaign.brief.mdlanding-page -> claude/skills/ijfw-new-project/templates/landing-page.brief.mddesign-system -> claude/skills/ijfw-new-project/templates/design-system.brief.mdlaunch -> claude/skills/ijfw-new-project/templates/launch.brief.mdIf the template file is absent in this checkout, fall back to a minimal skeleton (goal / audience / success criteria / out-of-scope / first move). Templates are the contract; the skill must still produce a brief if they haven't shipped yet.
The skeleton fields are domain-shaped, not software-shaped:
book -> premise / reader / chapter spine / voice / publication targetcampaign -> offer / audience / channels / KPI / objection maplanding-page -> promise / proof / CTA / scroll narrative / metricdesign-system -> tokens / primitives / patterns / governance / consumerslaunch -> PR/FAQ / target date / channels / readiness gatesWalk the user through the brief in order. ONE question per turn. Echo back
every 3 turns: So far: <2-line recap>. Yes?
Never paste the empty template and wait. Never dump a numbered list. The
brainstorm-discipline invariants from ijfw-workflow apply: one question,
no offscreen research, no silent advance, visible deliverable.
If the user gives a thin answer, do one 5-Why drill, then move on. If they
say enough or skip, stop filling and move to LOCK with what you have.
After brief is full, ask once: Want a milestone roadmap stub now, or jump to first move?
On roadmap: write .planning/ROADMAP.md with 3-5 milestones inferred from
the brief. Each milestone is one line: name + success criterion. No tasks
yet -- that belongs to ijfw-plan per milestone.
On jump: skip ROADMAP. The brief alone is enough to start.
Mark the active milestone with .planning/<milestone>/ directory + an empty
MILESTONE.md placeholder. Future planning skills key off this directory.
Call ijfw_memory_store with:
key: project_metavalue: JSON object {domain, name, brief_path, created_at, milestone}This is the single source of project type identity for downstream skills.
ijfw-design, ijfw-plan-check, ijfw-workflow, ijfw-verify, and
ijfw-ship all read project_meta.domain to adapt their checklists.
Paste the brief back in-chat (max 8 lines) and end:
Project locked. Brief at .ijfw/memory/brief.md. Domain: <domain>.Next: <recommended-next-skill>(software ->ijfw-plan, book -> chapter outline, campaign -> offer matrix, etc.)
Invoke the ijfw-agents-md skill with intent context (brief.md). It will
seed AGENTS.md and the platform adapter (CLAUDE.md, GEMINI.md, etc.) only
if those files are absent. Already-present files are left untouched.
software / landing-page.DOMAIN: <detected or chosen>
BRIEF: .ijfw/memory/brief.md (<N> lines)
ROADMAP: .planning/ROADMAP.md (<N> milestones) | skipped
MEMORY: project_meta stored
NEXT: <recommended next skill or command>© FerroxLabs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 6 other files in claude/skills/ijfw-new-project of FerroxLabs/ijfw.
Open the folder on GitHubat commit eda62f3
Ijfw New Project next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ijfw New Project this skillFerroxLabs/ijfw | 212 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Figma Buildawdr74100/figwright | 1k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Impeccablebestofjs/bestofjs | 3.1k | 26 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Design Taste Frontendcaorushizi/oss-client | 113 | 22 repos | ~22k | Automated safety check: Pass | None | |
| UI/UX Design System AdvisorGalaxy-Dawn/claude-scholar | 5.7k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Design StyleCastor6/tactus | 376 | 1 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 |
awdr74100/figwright
Build a Figma design from code or a description — the reverse of figma-codegen.
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
caorushizi/oss-client
Anti-slop frontend skill for landing pages, portfolios, and redesigns.
Galaxy-Dawn/claude-scholar
Turns a vague UI request into a concrete design system with style, palette, typography and layout guidance from a search script, plus stack-specific implementation advice.
Castor6/tactus
A skill your agent uses whenever the user asks to build, create, design, develop, improve, or style any frontend interface or visual element.
ZeroZ-lab/cc-design
High-fidelity HTML design and prototype creation. An agent skill from ZeroZ-lab/cc-design.
FerroxLabs/ijfw
Maintain canonical AGENTS.md (open spec). An agent skill from FerroxLabs/ijfw.
FerroxLabs/ijfw
A skill your agent uses when the user says: 'design', 'redesign', 'UI', 'UX', 'dashboard', 'page', 'component', 'make it look better', 'polish', 'pretty', 'professional', 'user experience'…
FerroxLabs/ijfw
A skill your agent uses when a milestone is shipping and you need to archive its artifacts, generate a summary, and seed the next milestone.
FerroxLabs/ijfw
Challenge decisions, surface counter-arguments, flag assumptions.
FerroxLabs/ijfw
Generate a cross-platform multi-model audit (Trident) on a diff, brief, or artifact.
FerroxLabs/ijfw
Root-cause analysis with hypothesis tracking. An agent skill from FerroxLabs/ijfw.
Categories
Bootstrap a fresh project of any domain -- software, book, marketing campaign, landing page, design system, or product launch. Ijfw New Project is an agent skill from FerroxLabs/ijfw. Bootstrap a fresh project of any domain -- software, book, marketing campaign, landing page, design system, or product launch.
Ijfw New Project fits situations like: tasks that involve Project scaffolding; tasks that involve Landing pages; tasks that involve Design systems.
Run `npx skills add FerroxLabs/ijfw --skill ijfw-new-project -a claude-code`. Or copy the skill folder (claude/skills/ijfw-new-project in FerroxLabs/ijfw) into .claude/skills/ijfw-new-project in your project. Claude Code loads it when a task matches its description.
Run `npx skills add FerroxLabs/ijfw --skill ijfw-new-project -a codex`. Or copy the skill folder (claude/skills/ijfw-new-project in FerroxLabs/ijfw) into .agents/skills/ijfw-new-project in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/ijfw --skill ijfw-new-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ijfw-new-project, .gemini/skills/ijfw-new-project, .github/skills/ijfw-new-project and .opencode/skills/ijfw-new-project in your project.
SKILL.md names no scripts, command-line tools or credentials: Ijfw New Project is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Ijfw New Project is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Ijfw New Project: Figma Build (awdr74100/figwright, 1k stars), Impeccable (bestofjs/bestofjs, 3.1k stars), Design Taste Frontend (caorushizi/oss-client, 113 stars) and UI/UX Design System Advisor (Galaxy-Dawn/claude-scholar, 5.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
FerroxLabs (a GitHub user) maintains it in FerroxLabs/ijfw, which has 212 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on October 5, 2026.
Source: FerroxLabs/ijfw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.