How do I install the Conventions skill?

Run npx skillmds@latest add pcatattacks/conventions 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.

Is Conventions 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 Conventions?

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 Conventions free to use?

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

Who published Conventions?

pcatattacks (@pcatattacks) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Conventions by pcatattacks — Agent Skill

Name: Conventions
Rating: 4.5 (4 reviews)
Author: pcatattacks

File contents

Solopreneur Conventions

These conventions are the single source of truth for shared formats across the solopreneur workflow.

Ticket Schema

Tickets are YAML-frontmatter markdown files in .solopreneur/backlog/{project}/:

---
id: MVP-001
title: Short descriptive title
priority: MVP | P1 | P2
type: eng | design | eng+design
status: pending | in-progress | built | tested | done
depends_on: []
blocks: []
design_ref: .solopreneur/designs/{dir}/{screen}.html
branch: ticket/{ID}
worktree: /path/to/worktree
---

## Description
What this ticket implements and why.

## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2

## Technical Notes
Stack choices, approach, risks.

## Files
(Populated during build)

Status Transitions

pending       → in-progress   (build starts)
in-progress   → built         (build completes)
built         → tested        (QA passes in review)
tested        → done          (merged to main in review)

Where Transitions Happen

Skills contain the operational instructions for the orchestrator. If the state machine changes, update these locations:

pending → in-progress: build/SKILL.md (line 43), sprint delegates to build
in-progress → built: build/SKILL.md (line 150), sprint/SKILL.md (line 99)
built → tested: review/SKILL.md (line 51)
tested → done: review/SKILL.md (lines 58, 99)

Review Severity Format

When producing review findings, rate every issue:

Critical: Breaks functionality, security vulnerability, data loss risk. Must fix before proceeding.
Warning: Incorrect behavior in edge cases, missing validation. Should fix, not blocking.
Suggestion: Code quality improvement, better patterns available. Nice-to-have.
Positive: Things done well. Always include at least one.

Plan File Format

Implementation plans use this structure:

# Plan: [Feature Name]

## Context
[What we're building and why. Reference source spec/design if applicable.]
**Branch**: `ticket/{ID}` (if ticket build)

## Step N: [Short description]
**Files**: `path/to/file.ext` (create|modify)
**Do**: [Clear, specific instructions for what to write]
**Acceptance**: [Concrete criteria to verify this step is done]

---name: conventionsdescription: Shared conventions for the solopreneur workflow. Preloaded into agents via the skills frontmatter field.---# Solopreneur ConventionsThese conventions are the single source of truth for shared formats across the solopreneur workflow.## Ticket SchemaTickets are YAML-frontmatter markdown files in `.solopreneur/backlog/{project}/`:```yaml---id: MVP-001title: Short descriptive titlepriority: MVP | P1 | P2type: eng | design | eng+designstatus: pending | in-progress | built | tested | donedepends_on: []blocks: []design_ref: .solopreneur/designs/{dir}/{screen}.htmlbranch: ticket/{ID}worktree: /path/to/worktree---## DescriptionWhat this ticket implements and why.## Acceptance Criteria- [ ] Criterion 1- [ ] Criterion 2## Technical NotesStack choices, approach, risks.## Files(Populated during build)```### Status Transitions```pending → in-progress (build starts)in-progress → built (build completes)built → tested (QA passes in review)tested → done (merged to main in review)```### Where Transitions HappenSkills contain the operational instructions for the orchestrator. If the state machine changes, update these locations:- `pending → in-progress`: build/SKILL.md (line 43), sprint delegates to build- `in-progress → built`: build/SKILL.md (line 150), sprint/SKILL.md (line 99)- `built → tested`: review/SKILL.md (line 51)- `tested → done`: review/SKILL.md (lines 58, 99)## Review Severity FormatWhen producing review findings, rate every issue:- **Critical**: Breaks functionality, security vulnerability, data loss risk. Must fix before proceeding.- **Warning**: Incorrect behavior in edge cases, missing validation. Should fix, not blocking.- **Suggestion**: Code quality improvement, better patterns available. Nice-to-have.- **Positive**: Things done well. Always include at least one.## Plan File FormatImplementation plans use this structure:```markdown# Plan: [Feature Name]## Context[What we're building and why. Reference source spec/design if applicable.]**Branch**: `ticket/{ID}` (if ticket build)## Step N: [Short description]**Files**: `path/to/file.ext` (create|modify)**Do**: [Clear, specific instructions for what to write]**Acceptance**: [Concrete criteria to verify this step is done]```

Frequently asked questions

Conventions