GitHub
kb
Knowledge base for session continuity. Maintains project documentation with fixed directory structure (.pmc/docs/) and formats for PRDs, SOPs, tickets (T0000N), patterns, decisions, code maps, research, and sta...
☆ 0View skill
jayprimer AI Skills
GitHub ↗Browse published AI skills maintained by jayprimer. Compare skill descriptions and follow each source repository for setup instructions.
Author statistics
Indexed skills
15Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Popular categories
Recent indexing activity
Browse skills
GitHub
ticket-status
Programmatic verification of KB state: tickets, phases, tests, integrity. Provides scripts for automated checking at each workflow stage. SCRIPTS: - check_ticket.py: Ticket docs, tests, final status → next ste...
☆ 0View skill
GitHub
reflect
Perform reflection after completing work to capture learnings in KB. Ensures knowledge is preserved for future sessions. WHEN TO USE: - After completing a ticket (before archiving) - After completing a phase -...
☆ 0View skill
GitHub
update-kb
Synchronize knowledge base documentation with current codebase implementation. Performs full, incremental, or targeted audits of source code and updates code maps, PRDs, patterns, SOPs, and user-facing docs to...
☆ 0View skill
GitHub
dev
Orchestrate KB development workflow from request to completion. Coordinates skills in sequence: kb → plan → test → validate → complete → reflect → inbox. WORKFLOW: 1. LOOKUP - /pmc:kb (check existing PRDs, pat...
☆ 0View skill
GitHub
lint-kb
Validate and enforce KB documentation formats, completeness, and integrity. Checks recent docs (uncommitted or last N commits) against KB standards. CHECKS PERFORMED: 1. FORMAT - Documents follow required temp...
☆ 0View skill
GitHub
test
Execute tests following TDD cycle: RED (verify test fails) → GREEN (implement to pass) → REFACTOR. Interprets tests.json and performs steps using available tools (browser MCP, API, CLI, etc.). WHEN TO USE: - S...
☆ 0View skill
GitHub
plan
Plan development work following KB skill's structured approach with PRDs, phases, tickets, TDD specifications, and parallel execution planning. WORKFLOW: 1. KB LOOKUP - Check existing PRDs, patterns, code maps...
☆ 0View skill
GitHub
inbox
Process pending items from 0-inbox/ task queue. Assess scope and create appropriate KB artifacts (tickets, phases, PRDs). WHEN TO USE: - After completing primary work (ticket, phase, user request) - User says...
☆ 0View skill
GitHub
memory
PMC memory system for persistent context across sessions. Store, search, and retrieve project knowledge using semantic vector search (OpenAI embeddings) and full-text keyword search. Use when: storing importan...
☆ 0View skill
GitHub
plan-validation
Validate planning documents before implementation begins. Checks ambiguity resolution, prerequisites, and testing methods. Use when: - Before starting implementation of a ticket - User says "validate plan", "c...
☆ 0View skill
GitHub
lint-skill
Validate skill documents against PMC skill design principles. Checks format ownership, composite skill structure, and internal consistency. CHECKS: 1. FORMAT OWNERSHIP - kb skill owns all format templates (kb/...
☆ 0View skill
GitHub
complete
Finalize a completed ticket: write 5-final.md, update 4-progress.md, commit. WHEN TO USE: - All required tests pass (via /pmc:ticket-status) - Ready to mark ticket as COMPLETE or BLOCKED - User says "complete...
☆ 0View skill
GitHub
workflow
Develop, test, and register PMC workflows. Workflows are JSON state machines for Claude CLI, shell, sub-workflows. WORKFLOW: 1. DEFINE - Create workflow JSON with states, transitions 2. VALIDATE - pmc validate...
☆ 0View skill
GitHub
validate
Verify test execution by replaying trajectory and checking script coverage. Ensures tests actually happened as recorded and scripts cover all test cases. WHEN TO USE: - After tests claim to pass (verify they a...
☆ 0View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.