source-command-prime
Skill0 starsChanged 6 months agoMITView on GitHub
Orient on the codebase before starting any work
In this repository55 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-developmentSkill
- agent-teamsSkill
- ai-sdkSkill
- analyzing-financial-statementsSkill
- cache-componentsSkill
- chrome-devtoolsSkill
- Codex-automation-recommenderSkill
- Codex-md-improverSkill
- code-reviewSkill
- Command DevelopmentSkill
- creating-financial-modelsSkill
- data-visualizationSkill
- debugSkill
- develop-ai-functions-exampleSkill
- evolve-ai-layerSkill
- excalidraw-diagramSkill
- find-skillsSkill
- frontend-designSkill
- Hook DevelopmentSkill
- make-skill-templateSkill
- markdown-to-htmlSkill
- mcp-builderSkill
- MCP IntegrationSkill
- pdfSkill
- playwrightSkill
- Plugin SettingsSkill
- Plugin StructureSkill
- refactorSkill
- researchSkill
- security-best-practicesSkill
- skill-creatorSkill
- Skill DevelopmentSkill
- smithery-ai-cliSkill
- source-command-commit-and-deploySkill
- source-command-commitSkill
- source-command-create-prdSkill
- source-command-create-rulesSkill
- source-command-empty-redeploySkill
- source-command-evaluateSkill
- source-command-executeSkill
- source-command-handoffSkill
- source-command-plan-featureSkill
- source-command-reviewSkill
- source-command-self-healSkill
- source-command-validateSkill
- sql-queriesSkill
- statistical-analysisSkill
- vscode-ext-localizationSkill
- webapp-testingSkill
- web-artifacts-builderSkill
- web-design-guidelinesSkill
- Writing Hookify RulesSkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill when the user asks to run the migrated source command prime.
- Distinctive: line 23
Read these files (skip any that don't exist):
- Distinctive: line 36
Read key config files:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
source-command-prime
Use this skill when the user asks to run the migrated source command prime.
Command Template
Prime: Load Project Context
Objective
Build a mental model of this codebase so you can make informed decisions about what to build next.
Process
1. Read Core Documentation
Read these files (skip any that don't exist):
AGENTS.md— global rules and conventionsPRD.mdor.codex/PRD.md— product requirementsREADME.md— project overview- Any architecture docs referenced in AGENTS.md
2. Explore Project Structure
tree -L 3 -I 'node_modules|__pycache__|.git|dist|build|.next|venv*|.venv' 2>/dev/null || find . -maxdepth 3 -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/dist/*' -not -name '*.pyc' | head -80Read key config files:
package.json,pyproject.toml,Cargo.toml(whichever exists)tsconfig.json,vite.config.*,next.config.*(if present)- Database config/schema files
3. Check Git History (Long-Term Memory)
git log -15 --oneline 2>/dev/null
git status 2>/dev/null
git branch --show-current 2>/dev/null
git worktree list 2>/dev/null4. Identify Key Entry Points
Based on structure, read the first 50-80 lines of:
- Main entry points (index.ts, main.py, app.py, etc.)
- Core route/handler files
- Key model/schema definitions
5. Check for Pending Work
Look for:
HANDOFF.md— previous session left notes.codex/plans/*.md— pending implementation plans- Open TODOs in recent commits
If HANDOFF.md exists, cross-reference its open items against git log to verify they're still relevant. The vet-handoff hook may have already flagged stale items at session start — check for "HANDOFF.md Vet" warnings in the session transcript and act on them. Remove or mark completed any items that git history shows have been addressed. If all items are resolved, note that the handoff is fully resolved and can be deleted.
Output Report
Summarize in under 300 words with bullet points:
Project Overview
- What this project does
- Tech stack and key libraries
- Current state (early, mid-build, mature)
Architecture
- How code is organized
- Key patterns and conventions
- Important files and directories
Current State
- Active branch and recent work
- Any uncommitted changes
- Active worktrees and their feature branches (if any)
- Pending plans or handoffs
- Handoff status: which items are resolved vs. still open, whether HANDOFF.md should be cleaned up or deleted
Recommended Next Action
- What phase from the PRD comes next (if greenfield)
- What the most impactful next task is
- Any blockers or setup needed first
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

