Seed Conventions
Generate CLAUDE.md and CONVENTIONS.md for a brand-new project through a brief interview, and create the specs/ directory with evolved bigpowers structure (product/, tech-architecture/, verifications/, epics/archive/). Entry point for greenfield projects. Use when starting a new project from scratch, when user asks to set up AI agent conventions, or when there is no CLAUDE.md yet.
Install
npx skills add danielvm-git/bigpowers --skill seed-conventionsgit clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p ~/.claude/skills
cp -r /tmp/bigpowers/.cline/skills/seed-conventions ~/.claude/skills/seed-conventionsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Seed Conventions > **HARD GATE** — Before any new code lands, confirm the project conventions are understood. Ask: 'What does a good commit message look like in this project?' Bootstrap a new project with the AI agent conventions it needs. Run this once at the start of a greenfield project. ## What this creates - `CLAUDE.md` — Claude Code session config (project-specific) - `CONVENTIONS.md` — shared rules for all AI agents - `specs/` — the specs directory where all planning output will live - `AGENTS.md` — for OpenCode and other agents (optional) - `GEMINI.md` — for Gemini CLI (optional) ## Interview Ask the user these questions (one at a time, wait for each answer): 1. **Project name and one-sentence description** — "What is this project? One sentence." 2. **Stack** — "What language, framework, and runtime? (e.g. TypeScript / Next.js / Node 22)" 2b. **Stack profile (optional)** — Offer: `swift`, `typescript-vue`, `node-service`, or none. If chosen, merge the matching fragment from `profiles/<name>.md` into generated `CONVENTIONS.md`. 3. **Commands** — "What commands do you use for: run, test, build, lint?" 3b. **Preflight (optional)** — "What command runs test, lint, and build together? If none, chain Test + Lint + Build into one **Preflight** row." 4. **Architecture** — "Key modules and relationships in 1–2 sentences." 5. **Conventions** — "Any naming, file organization, or patterns all agents must follow?"
Details
- Skill name
seed-conventions- Repository
- danielvm-git/bigpowers
- Path
.cline/skills/seed-conventions/SKILL.md- License
- MIT
- Repo updated
- 9 November 2026
FAQ
What does the Seed Conventions skill do?
Generate CLAUDE.md and CONVENTIONS.md for a brand-new project through a brief interview, and create the specs/ directory with evolved bigpowers structure (product/, tech-architecture/, verifications/, epics/archive/). Entry point for greenfield projects. Use when starting a new project from scratch, when user asks to set up AI agent conventions, or when there is no CLAUDE.md yet.
How do I install the Seed Conventions skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add danielvm-git/bigpowers --skill seed-conventions. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Seed Conventions popular?
It lives in danielvm-git/bigpowers, which has 292 GitHub stars and 23 forks.
Related skills
Align Grid
292danielvm-git/bigpowers
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one. Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the hard-won front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay that lives in the SAME content box as the content, subgrid "bands" so every element snaps to a column line, an 8px baseline lock, and runtime OPTICAL ALIGNMENT that puts display type's i
Assess Impact
292danielvm-git/bigpowers
Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT_LATEST.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks "what does this break?".
Audit Code
292danielvm-git/bigpowers
Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.
Simulate Agents
292danielvm-git/bigpowers
Run Mock User and Auditor agents against a feature in fresh contexts before human review. Use after verify-work, before request-review, when user wants pre-review simulation.
Run Evals
292danielvm-git/bigpowers
Eval-Driven Development — define capability and regression evals before building; code graders use verify commands, model graders use explicit rubrics; log pass@k. Use before develop-tdd on new features, or when measuring agent capability over runs.
System Prompt Structure
207Owl-Listener/ai-design-skills
Anatomy of effective system prompts — role, context, constraints, format.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.