Skills Catalog

Skills live in exactly one place: fit-solutions/.agent/skills/.

They are never copied. A repo enables a skill with one line in its .agent/CONTEXT.md:

declared skills:
  - prp
  - brand-check
  - astro

Remove the line and the skill is gone. Add it and the skill is loaded. The skill file itself never changes per repo. That is the whole point.

What follows is the current roster. Canonical source for every entry is fit-solutions/.agent/skills/ — read the file before relying on what is below.

Planning and review

Skill	What it enables
prp	Full PRP / PIV methodology — PRD → plan → implement → validate → evidence. See PRP Workflow.
prp-cross-repo	Cross-repo PRP planning from fit-solutions root; handoff packets to target repos.
repo-spin-up	Checklist for generating a new client repo from a template.
org-audit	Registry integrity checks across repos.yaml, agents.yaml, solutions.yaml, tiers.yaml.
tier-check	Validates a proposed feature lands in the correct tier (Lite / Pro / Premium).
brand-check	Validates names, voice, and naming patterns against the brand registry.

Persona

Skill	What it enables
vp-ai-strategy	Loads the Quinn persona — strategic advisor and governance authority. Triggered when John addresses Quinn by name.
client-onboarding-skill	New-client intake workflow, scoped to the discovery → kickoff hand-off.

Web stack

Skill	What it enables
astro	Astro build patterns, Starwind Pro integration, FIT Web template conventions.
nextjs	Next.js patterns for the planned saas platform and the marketing site rebuild.
vercel	Vercel deployment patterns, project registry, and platform constraints.
supabase	Schema-per-client patterns, RLS, and migrations (see ADR-008).

Documentation and knowledge

Skill	What it enables
docs-craft	MkDocs Material patterns used in FIT Docs Lite and Pro templates.
obsidian-markdown	Obsidian-flavoured markdown patterns used inside the Vault.
obsidian-bases	Vault Bases — Obsidian database-style views.
obsidian-cli	Programmatic Vault edits from outside Obsidian.
quickadd	QuickAdd macros and capture templates.
templater	Templater templates inside the Vault.
json-canvas	Obsidian Canvas (.canvas) JSON authoring.
modal-form	Modal Forms plugin patterns.
defuddle	Cleaning dirty docs before ingestion.

n8n automation

Skill	What it enables
n8n	n8n workflow patterns and conventions.
n8n-workflow	Workflow authoring with deterministic boundaries.
n8n-workflow-patterns	Reusable patterns across FIT n8n flows.
n8n-code-javascript	Code node patterns (JavaScript).
n8n-expression-syntax	n8n expression language conventions.
n8n-node-configuration	Node configuration patterns and gotchas.
n8n-validation-expert	Validation of n8n workflows pre-deploy.
n8n-env-audit	Environment audit for n8n instances.
n8n-mcp-tools-expert	MCP tool usage inside n8n flows.

How a new skill gets added

From SKILLS-HOWTO-v2.md:

1. Open fit-solutions/.agent/skills/.
2. Copy an existing skill file as a starting point (prp.md is the canonical pattern).
3. Required sections: What this skill enables · When to use · Core content · Enabled in these repos by default.
4. Update fit-solutions/registry/repos.yaml — add the new skill to declared skills for every repo that should use it.
5. Commit.

Skipping step 4 means the skill exists but no repo declares it. The agent cannot see undeclared skills. That is by design.

What this means for an agent

When you load into a repo, your first action is to read the repo’s .agent/CONTEXT.md, find the declared skills: block, and read only those skill files from fit-solutions/.agent/skills/.

If the task in front of you requires a capability that is not in the enabled list, surface the gap. Do not improvise. Improvising a skill is how deterministic systems become non-deterministic.

Next

Evidence — what gets written down after the work is done.