ericrisco/rsc-harness / skills/init
init
FlaggedUse 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.8 KB |
| evals/README.md | markdown | 2.9 KB |
| evals/cases.yaml | config | 6.5 KB |
| references/accompaniment-and-profile.md | markdown | 6.0 KB |
| references/discovery.md | markdown | 5.8 KB |
| references/recommend-skills.md | markdown | 6.9 KB |
| scripts/verify.shexecutable | script | 4.3 KB |
references/recommend-skills.md
View on GitHub# Recommend Skills — the skill map, sample printouts & the "siempre 3 opciones" pattern
Phase 3 detail. Map discovery to individual rsc skills, print the exact
`npx @ericrisco/rsc add` commands, and run the requirements-first 3-option decision pattern
for any significant choice. A skill **cannot install anything** — it recommends
and prints commands the user runs.
## The skill map
| Discovery signal | Skills | One-line *why* (in the user's register) |
| --- | --- | --- |
| Always (every project) | `harness` | The control plane — scaffolds and governs the whole workspace (`suggest` installs with it as the floor). |
| Backend / API / database | `fastapi` or `go`, `postgresdb` | The server, the API, the database that remembers things. |
| Web or mobile UI | `nextjs` or `flutter`, `design` | The screens people actually see and tap. |
| Marketing / landing / decks / teaching | `marketing`, `presentations`, `course-storytelling` | The words, slides, and lessons that explain and sell it. |
| AI agents | `building-agents` | Agents that use tools and reason over your data. |
| Security & shipping / ops (incl. non-code company harness connecting tools) | `security-audit`, `deployment` | Ship it safely and wire up the external tools (email, payments, hosting). |
Recommend a skill **only if discovery justified it** — same discipline as "no
speculative tools". Don't recommend `building-agents` because agents are trendy;
recommend it because the user said they want an agent.
Note on the non-code harness: a company/ops/research/content harness almost
always wants `harness` (the structure) + `deployment`/`security-audit` (to connect
external tools and handle credentials securely), and often `marketing`. It
usually does NOT want `fastapi`/`nextjs` unless they're also building software.
## What to print
One `npx @ericrisco/rsc add` line per recommendation (or batch them on one line), each with
its *why* in the user's language and register.
```text
npx @ericrisco/rsc add <skill> [<skill> ...]
```
### Sample printout — software, full-stack web app with marketing
```text
Based on what you described (a web app with a backend, a Next.js UI, a landing
page, and you want to ship it securely), install these:
npx @ericrisco/rsc add harness # the control plane — scaffolds and governs the workspace
npx @ericrisco/rsc add fastapi postgresdb # the API and the database
npx @ericrisco/rsc add nextjs design # the web UI people see
npx @ericrisco/rsc add marketing # the words for your landing page
npx @ericrisco/rsc add security-audit deployment # ship it safely
Once they're installed, run the harness skill and I'll build the project structure.
```
### Sample printout — non-code harness, running an agency's operations
```text
You're organizing how your agency runs — client emails, contracts, invoicing,
and you want it all findable. That's a non-code harness; install:
npx @ericrisco/rsc add harness # your 01-TOOLS (connections) + 02-DOCS (your second brain)
npx @ericrisco/rsc add security-audit deployment # connect email, payments, drive — and keep credentials safe
npx @ericrisco/rsc add marketing # for the proposals, decks and copy you send clients
Once installed, run the harness skill and I'll set up the structure that holds it all.
```
### Sample printout — greenfield AI agent
```text
You want an AI agent that answers questions over your own documents. Install:
npx @ericrisco/rsc add harness # the control plane
npx @ericrisco/rsc add building-agents # agent loops, tools, RAG
npx @ericrisco/rsc add fastapi postgresdb # an API + database to serve it
npx @ericrisco/rsc add security-audit deployment # ship it safely
Then run the harness skill.
```
## The "siempre 3 opciones" decision pattern
For any significant decision — deploy target, database, framework, hosting, which CRM, where documents live — never decide silently and never dump ten choices. Four steps:
### 1. Gather the driving requirements first
Ask only the questions that actually change the answer, in one short batch. Checklists per decision type:
- **Deploy target:** expected number of users; concurrent users; budget; data region / residency rules; the team's comfort operating servers; scaling needs (steady vs spiky); existing org/cloud constraints.
- **Database:** data shape (relational vs documents vs key-value); expected size and growth; query patterns; consistency vs scale needs; managed vs self-hosted preference; budget.
- **Framework / language:** team's existing skills; the surfaces needed; performance constraints; ecosystem/libraries required; hiring/longevity.
- **Where knowledge/documents live (non-code harness):** volume and formats; who needs access; privacy / residency of client data; search needs; existing tools already paid for.
### 2. Present EXACTLY three options
Three, with honest trade-offs — what each is good at, what it costs, what it demands. Not two (false binary), not ten (paralysis). If a fourth is genuinely worth knowing, mention it in one line under the third — but the choice is between three.
### 3. Recommend one, matched to their answers
State your recommendation and why, in their register. For a `non-technical` user, explain each option with an everyday analogy and check they followed before they pick.
### 4. Log the decision
Once they choose, append an entry to `02-DOCS/wiki/harness/decisions.md` (format in `accompaniment-and-profile.md`): context (the requirements you gathered), the three options, the decision, and why.
## Canonical worked example — deploy target
Requirements gathered: ~500 users, ~20 concurrent, low budget, EU data residency required, small team comfortable with a little server work, steady (non-spiky) traffic.
> **Option 1 — Hetzner VPS + Coolify.** Cheapest by far (a capable box is a few euros a month), total control, and Hetzner has EU regions so residency is covered. The catch: you self-manage the server — updates, backups, keeping it up. Coolify makes deploys push-button, but the box is yours.
>
> **Option 2 — Vercel.** Zero-ops: you push, it deploys, it scales itself, nothing to maintain. The catch: it gets expensive as you grow, and you're shaped by its model (best for frontend/serverless; data residency and always-on backends need care).
>
> **Option 3 — Fly.io.** Managed containers that run in an EU region close to your users, simpler than raw cloud, more hands-off than a VPS. The catch: a bit pricier than Hetzner and you still think in containers.
>
> **Recommendation:** Option 1 (Hetzner + Coolify, EU region). Your budget is tight, EU residency is a hard requirement Hetzner satisfies cleanly, traffic is steady so you don't need autoscaling, and your team is fine managing one box. We log this and move on; if ops ever becomes a burden, Option 3 is the easy step up.
This decision triggers the `deployment` skill at build time, which knows Hetzner+Coolify, Vercel, Fly.io and the rest in depth. `init` makes the choice and records it; `deployment` executes it.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 471k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Unverified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |