How do I install the Project Meta skill?

Run npx skillmds@latest add persimmon-automation-labs/project-meta in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Project Meta skill do?

Project-Meta — Index It is listed under Coding & Dev Tools on SkillMD.

Is Project Meta safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Project Meta?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Project Meta free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Project Meta?

Persimmon-Automation-Labs (@persimmon-automation-labs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Project Meta by persimmon-automation-labs

Name: Project Meta
Rating: 4.666666666666667 (3 reviews)
Author: Persimmon-Automation-Labs

File contents

Project-Meta — Index

Repo lifecycle, documentation, and onboarding for Persimmon projects. This mother is a map; follow the child for the actual work.

Trigger

"Start a new client project" / "onboard" / "SOW"
"Audit the docs" / "update README" / "add an ADR"
"Walk me through this project" / "where does X come from?"
"Write the deployment plan / go-live doc"
"Set up / sync the Persimmon skills"

The child skills

Skill	When to use	Owns
`meta-new-client-project`	New engagement	GitHub repo in the org, clone, scaffold docs, register in CLAUDE.md/README
`meta-document-project`	Doc maintenance	Lean doc audit/scaffold/update — enforces Persimmon doc conventions
`meta-project-xray`	Understanding a codebase	Interactive guided walk-through of pages, data flows, integrations
`meta-adr-authoring`	Recording a decision	MADR-lite ADRs in `docs/decisions/` for non-obvious choices
`meta-deployment-plan`	Go-live	Client-facing deployment plan document with sign-off
`meta-skill-sync`	Wiring skills into a project	Install the Persimmon plugin (marketplace), verify activation, onboard a dev

How to route

Brand-new project? → meta-new-client-project, then the master persimmon lifecycle tree.
Docs drifting / missing? → meta-document-project.
Need to understand the code? → meta-project-xray.
Non-obvious decision? → meta-adr-authoring.
Shipping to the client? → meta-deployment-plan (+ quality-final-review).
Skills not active in a repo? → meta-skill-sync.

Doc conventions — one-screen summary (every client folder gets exactly)

CLAUDE.md — dev context (starts with a "What This File Is" preamble)
README.md — human onboarding (status table, team, docs table)
docs/reference/scope-of-work.md — signed SOW (ONLY place for financials)
docs/decisions/ — ADRs (MADR-lite)
docs/specs/ & docs/plans/ — workflow artifacts (see workflow)
notes/ — meeting notes, requirements
.github/workflows/ci.yml — lint, typecheck, prisma validate, build

Never put payment terms in README, architecture in README (link to CLAUDE.md), or client contact info in CLAUDE.md.

Anti-patterns banned

Financials anywhere but docs/reference/scope-of-work.md
Architecture in README instead of CLAUDE.md
Undocumented non-obvious decisions (write an ADR)
Hand-wiring skills via invalid settings keys — use meta-skill-sync (plugin install)

Relationship to other mothers

Mother	Connection
`workflow`	Specs/plans live alongside the docs this mother manages
`quality`	`meta-deployment-plan` pairs with `quality-final-review`
all	`meta-new-client-project` kicks off the full master lifecycle

---name: project-metadescription: Project-Meta — Index---# Project-Meta — IndexRepo lifecycle, documentation, and onboarding for Persimmon projects. This mother is a map; follow the child for the actual work.## Trigger- "Start a new client project" / "onboard" / "SOW"- "Audit the docs" / "update README" / "add an ADR"- "Walk me through this project" / "where does X come from?"- "Write the deployment plan / go-live doc"- "Set up / sync the Persimmon skills"## The child skills| Skill | When to use | Owns ||---|---|---|| `meta-new-client-project` | New engagement | GitHub repo in the org, clone, scaffold docs, register in CLAUDE.md/README || `meta-document-project` | Doc maintenance | Lean doc audit/scaffold/update — enforces Persimmon doc conventions || `meta-project-xray` | Understanding a codebase | Interactive guided walk-through of pages, data flows, integrations || `meta-adr-authoring` | Recording a decision | MADR-lite ADRs in `docs/decisions/` for non-obvious choices || `meta-deployment-plan` | Go-live | Client-facing deployment plan document with sign-off || `meta-skill-sync` | Wiring skills into a project | Install the Persimmon plugin (marketplace), verify activation, onboard a dev |## How to route1. **Brand-new project?** → `meta-new-client-project`, then the master `persimmon` lifecycle tree.2. **Docs drifting / missing?** → `meta-document-project`.3. **Need to understand the code?** → `meta-project-xray`.4. **Non-obvious decision?** → `meta-adr-authoring`.5. **Shipping to the client?** → `meta-deployment-plan` (+ `quality-final-review`).6. **Skills not active in a repo?** → `meta-skill-sync`.## Doc conventions — one-screen summary (every client folder gets exactly)- `CLAUDE.md` — dev context (starts with a "What This File Is" preamble)- `README.md` — human onboarding (status table, team, docs table)- `docs/reference/scope-of-work.md` — signed SOW (ONLY place for financials)- `docs/decisions/` — ADRs (MADR-lite)- `docs/specs/` & `docs/plans/` — workflow artifacts (see `workflow`)- `notes/` — meeting notes, requirements- `.github/workflows/ci.yml` — lint, typecheck, `prisma validate`, build**Never put** payment terms in README, architecture in README (link to CLAUDE.md), or client contact info in CLAUDE.md.## Anti-patterns banned- Financials anywhere but `docs/reference/scope-of-work.md`- Architecture in README instead of CLAUDE.md- Undocumented non-obvious decisions (write an ADR)- Hand-wiring skills via invalid settings keys — use `meta-skill-sync` (plugin install)## Relationship to other mothers| Mother | Connection ||---|---|| `workflow` | Specs/plans live alongside the docs this mother manages || `quality` | `meta-deployment-plan` pairs with `quality-final-review` || all | `meta-new-client-project` kicks off the full master lifecycle |

Frequently asked questions

Project Meta