Skip to content

ericrisco/rsc-harness / skills/init

Use when starting from nothing or pointing rsc at an existing project — the front door. First asks one question — technical terms or analogies (analogies by default) — then discovers what the user wants to build or govern (any stack, or a non-code harness: company/ops, research, knowledge, content), writes the profile to 02-DOCS, and installs the skills discovery justified. NOT the scaffolder (that is `harness`), NOT a stack skill.

FileKindSize
SKILL.mdskill md12.8 KB
evals/README.mdmarkdown2.9 KB
evals/cases.yamlconfig6.5 KB
references/accompaniment-and-profile.mdmarkdown6.0 KB
references/discovery.mdmarkdown5.8 KB
references/recommend-skills.mdmarkdown6.9 KB
scripts/verify.shexecutablescript4.3 KB

evals/cases.yaml

View on GitHub
skill: init

# Cases for the rsc-skills "init" front door / bootstrapper.
# init profiles the user (one question: technical terms or analogies), discovers what
# they want to BUILD or GOVERN (code OR a non-code harness), recommends rsc
# skills, and hands off to the harness skill. It is NOT the scaffolder and NOT
# a specific stack skill.

should_trigger:
  - prompt: "Quiero montar un proyecto nuevo pero no sé por dónde empezar."
    why: "Canonical greenfield entry with explicit uncertainty ('no sé por dónde empezar') — init's job is to ask the register, discover, and recommend before anything is built."

  - prompt: "I have an existing repo and I want to set up the harness on it. Where do I start?"
    why: "Brownfield bootstrapping: pointing the rsc harness at an existing project is exactly init's front-door role (detect greenfield vs brownfield, profile, recommend skills)."

  - prompt: "Acabo de instalar esto. ¿Qué hago primero?"
    why: "First-contact phrasing without naming any tool — init is the literal first thing you run; it should claim 'what do I do first' onboarding moments."

  - prompt: "Tengo una idea para una app pero soy de negocio, no técnico. Ayúdame a arrancar esto desde cero."
    why: "Greenfield + explicitly non-technical user — init leads with the one register question (technical or analogies), the core reason it exists, before any stack choice."

  - prompt: "I want to use this to run my company's operations, not to write code. Can I bootstrap that here?"
    why: "Non-code harness (company/ops) bootstrap — init is domain-agnostic and explicitly governs non-code harnesses the same way; this is a deliberately non-obvious trigger."

  - prompt: "Set me up. I want to build a personal knowledge base / wiki with this."
    why: "'Set me up' + a non-code knowledge-base goal: init profiles and recommends (likely harness, possibly marketing) then hands off to harness — it owns the setup conversation, not a specific stack skill."

  - prompt: "Bootstrap a workspace for a research program I'm planning."
    why: "Explicit 'bootstrap a workspace' for a non-code (research) domain — init's discover+recommend+handoff flow, including the iron rule that 'project' is not assumed to mean code."

should_not_trigger:
  - prompt: "Create a CLAUDE.md file documenting the architecture of this existing codebase."
    route_to: "none"
    why: "This is the built-in /init (CLAUDE.md generator), not the rsc-skills front door. init only writes the user-profile + a Knowledge-map link, and it does NOT scaffold or document the codebase — that is harness/other tooling. No rsc sibling owns generic architecture docs, so route to none."

  - prompt: "Run the scaffolding now — create the 01-TOOLS and 02-DOCS folders and wire up the structure."
    route_to: "harness"
    why: "init explicitly hands off scaffolding to the harness skill. The moment the user asks to actually BUILD 01-TOOLS/02-DOCS, it is harness's job, not init's (init writes only the profile + link)."

  - prompt: "Set up a FastAPI backend with a Postgres database for my new service."
    why: "User already knows the stack and wants a specific backend built — this is the fastapi/backend stack skill, not the profiling front door. init recommends skills; it does not implement stacks."
    route_to: "fastapi"

  - prompt: "Help me pick and configure a deploy target — Hetzner vs Vercel vs Fly.io — and ship it."
    why: "Although init uses the 3-option deploy example to illustrate the decision pattern, an actual 'configure and ship the deployment' request is the deployment ops skill's runtime job, which init only references."
    route_to: "deployment"

  - prompt: "Scaffold a new Next.js app with the App Router and Tailwind."
    route_to: "nextjs"
    why: "Concrete frontend build with a named framework — the nextjs stack skill. init would only ever recommend the nextjs skill, not scaffold the app itself."

  - prompt: "Review this auth code for security issues like injection and broken access control."
    route_to: "security-audit"
    why: "A security-only review of existing code, no bootstrapping or profiling involved — squarely the security-audit skill, not the front-door init."

capability:
  - scenario: "A non-technical founder says: 'I want to build an app to connect dog owners but I don't know where to start.' Show how init opens the engagement."
    must_include:
      - "Asks ONE first-contact question FIRST, before any discovery or recommendation ('¿Te hablo en lenguaje técnico o con analogías?'), and records technical_level as technical or non-technical"
      - "Asks no second calibration question (no accompaniment/verbosity level); given a silent or unclear answer, records non-technical and speaks with plain words and analogies"
      - "Persists the profile to 02-DOCS/wiki/harness/user-profile.md and an append-only 02-DOCS/wiki/harness/decisions.md, and links both from a ## Knowledge map section in root CLAUDE.md (creating CLAUDE.md if absent, additive only)"
      - "Detects greenfield vs brownfield rather than assuming, and runs DISCOVER (goals, audience, constraints, surfaces) before recommending"
      - "Recommends specific rsc skills matched to discovery (at minimum harness; nextjs/flutter + design if app surfaces justify it) and PRINTS the exact install commands (npx @ericrisco/rsc add <skill> ...)"
      - "Does NOT install anything itself and does NOT scaffold 01-TOOLS/02-DOCS — it hands off to the harness skill as the final step"
      - "Does not recommend speculative skills (e.g. building-agents) unless discovery justified them"

  - scenario: "A user with an existing multi-package repo says: 'Point the harness at my project and get me started.' Show the brownfield front-door flow."
    must_include:
      - "Still asks the one register question first — profile before anything, even on brownfield"
      - "Detects brownfield via manifests (package.json / pyproject.toml / pubspec.yaml / go.mod / Cargo.toml), source files, legacy XX-* folders, or existing 01-TOOLS/02-DOCS, with a read-only scan that ignores node_modules/.venv/.next/.git/dist/build"
      - "Summarizes the detected stack and current state and CONFIRMS with the user instead of assuming"
      - "Writes profile + decisions log under 02-DOCS/wiki/harness/ and adds the Knowledge-map link to CLAUDE.md without deleting existing content"
      - "Recommends skills matched to the detected stack and prints the exact install commands, recommending only what was justified"
      - "Hands off to the harness skill for the actual 01-TOOLS/02-DOCS scaffolding/migration rather than doing it inside init"
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall