agentleFS
DTiapanDTiapan/craft/skills/craft-adopt/SKILL.md

craft-adopt

Skill0 starsChanged 56 days agoMITView on GitHub

Bootstrap Craft into a target project: scaffold engineering ledger, wire AGENTS.md, install domain skill profiles, verify upstream skills are installed locally. Use when starting a new project, onboarding Craft, or user says "adopt craft" / "set up the ledger".

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After cloning Craft on a new machine (verify deps or setup domain profiles)

    line 33
  2. Distinctive:

    Run the 1-click installer:

    line 59
  3. Distinctive:

    Before claiming adopt complete:

    line 129

≈ “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

Craft Adopt

One workflow to make a project Craft-ready. Does not copy upstream skills — scaffolds project artifacts, installs domain skill profiles, and verifies local installs.


Quick Start: 1-Click Domain Skill Installer

From your Craft clone, run the unified installer for any domain profile (saas, engineering, product, uiux, all):

# 1-Click Install for specific domain profile
bash scripts/craft-install.sh --profile saas --project-dir /path/to/project

# Or install all profiles
bash scripts/craft-install.sh --profile all

When to use

  • New greenfield or brownfield project adopting Craft
  • User says: "adopt craft", "set up engineering ledger", "bootstrap craft", "install craft skills"
  • After cloning Craft on a new machine (verify deps or setup domain profiles)

When NOT to use

  • Questions about what Craft is (read README)
  • Adding a new skill to craft repo (use craft-promote or manual skill authoring)

Domain Skill Profiles

Craft v0.2.0 organizes skills into purpose-built domain profiles:

ProfileFocus AreaKey Skills
saasSaaS, billing, marketing, multi-tenancyAPI Design, Security, Frontend, UI/UX Pro, Launch
engineeringProduction architecture & core devTDD, Security, Observability, Performance, CI/CD, Git
product0 to 1 discovery & PRD authoringIdea Refine, Interview Me, Spec-Driven Dev, Task Breakdown
uiuxUI/UX & design systemsUI/UX Pro Max, Frontend UI, Browser DevTools, Web Guidance

Workflow

1. Verify machine dependencies & install profile

Run the 1-click installer:

bash scripts/craft-install.sh --profile saas

Or verify existing dependencies:

bash $CRAFT/skills/craft-adopt/scripts/verify-deps.sh

2. Scaffold ledger in target project

TARGET=/path/to/project
CRAFT=/path/to/craft   # local clone path

mkdir -p "$TARGET/docs/engineering-ledger"
mkdir -p "$TARGET/docs/decisions"

cp "$CRAFT/skills/engineering-ledger/templates/"* "$TARGET/docs/engineering-ledger/"

Initialize INDEX.md with project name, date, phase Shape, and link to AGENTS.md.

3. Wire AGENTS.md

Append (do not replace existing content):

## Craft (Orchestration, Skills & Ledger)

- **Read Ledger First**: Non-trivial work must read `docs/engineering-ledger/INDEX.md` and active phase in `phases.md` before taking action.
- **Mandatory Skill-First Routing**: Every discussion, architecture design, development, and debugging task **must flow through the corresponding skill** in `.agents/skills/`. Before executing any phase, cross-check installed skills and load the best domain skill:
  - *Ideation & Discovery*: Load `idea-refine` or `interview-me` to sharpen ambiguous requirements.
  - *System Architecture & Design*: Load `system-design` (stress-test failure modes, trade-offs, scaling, data models) along with building blocks (`api-design`, `architecture-diagram`, `caching`, `resilience-failure`, `data-storage`, `messaging-streaming`).
  - *Specification & Decisions*: Load `spec-driven-development`. For irreversible forks, create an ADR in `docs/decisions/` per `documentation-and-adrs`.
  - *Implementation & TDD*: Load `incremental-implementation` for thin slices and `test-driven-development` (Red-Green-Refactor).
  - *Debugging & Errors*: Load `debugging-and-error-recovery` (systematic root cause analysis, never guess).
  - *Verification & Quality*: Load `constraint-driven-development` and `code-review-and-quality` before completing features.
  - *UI / Frontend*: Load `ui-ux-pro-max` and `frontend-ui-engineering`.
- **Anti-Drift**: Use the single best skill for the active phase (via `using-craft`). Never bypass skills or invent ad-hoc processes when an established skill exists.
- **Phase Transition Thresholds**: Never jump phases without satisfying the previous phase's exit gate evidence in `phases.md`. Anti-drift thresholds must be verified before proceeding to prevent premature implementation.
- **Market Validation Gate**: In `docs/northstar.md`, evaluate the Market Validation Score (0–10). A score of >= 7/10 is required to enter `Build`. If < 7, stop or pivot.
- **Durable Ledger Updates**: Append tactical decisions (`DR-###`) and lessons (`LL-###`) to `docs/engineering-ledger/`, and update `INDEX.md` before ending substantive sessions.

4. Optional project manifest pointer

Create $TARGET/craft.project.yaml:

craft_version: "0.2.0"
profiles:
  - saas
  - engineering
ledger_path: docs/engineering-ledger
adr_path: docs/decisions
manifest_ref: DTiapan/craft craft.manifest.yaml

5. Initialize phases.md

Set first phase row to in_progress for current work (usually Shape or Build for brownfield).


Verification gate

Before claiming adopt complete:

  • docs/engineering-ledger/ has INDEX, phases, attack-plans, decisions, lessons
  • docs/decisions/ exists (may be empty)
  • AGENTS.md mentions Craft + ledger path
  • verify-deps.sh passes (or 1-click installer executed)
  • No upstream SKILL.md files copied into project

Anti-patterns

Don'tDo instead
Vendor Addy skills into .agents/skills/ in gitUse craft-install.sh or npx skills add on each machine
Replace entire AGENTS.mdAppend Craft section
Skip ledger on brownfieldBackfill INDEX with current phase + recent decisions

Artifacts

FileLocation
Ledger scaffolddocs/engineering-ledger/*
ADR directorydocs/decisions/
Project pointercraft.project.yaml (optional)
AGENTS.md sectionTarget project root

See also docs/adoption.md.

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.