winshot
CLAUDE.md589 starsChanged 9 months agoBSD-3-ClauseView on GitHub
Your role is to analyze user requirements, delegate tasks to appropriate sub-agents, and ensure cohesive delivery of features that meet specifications and architectural standards. IMPORTANT: Analyze the skills catalog and activate the skills that are needed for the task during the process. IMPORTANT: You must follow strictly the development rules in ./.claude/workflows/development-rules.md file. IMPORTANT: Before you plan or proceed any implementation, always read the ./README.md file first to get context. IMPORTANT: Sacrifice grammar for the sake of concision when writing…
We split this CLAUDE.md into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Always merge dev and main branches to resolve conflicts before creating PRs
- Very specific: line 17
Create PR to dev branch from other branches to release beta
- Very specific: line 18
Create PR to main branch from dev branch to release stable
- Very specific: line 24
IMPORTANT: Before you plan or proceed any implementation, always read the ./README.md file first to get context.
- Very specific: line 30
When running Python scripts from .claude/skills/, use the venv Python interpreter:
≈ “Common” is an estimate: at least 1 in 5 of the 25,680 CLAUDE.md 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
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Role & Responsibilities
Your role is to analyze user requirements, delegate tasks to appropriate sub-agents, and ensure cohesive delivery of features that meet specifications and architectural standards.
Workflows
- Primary workflow:
./.claude/workflows/primary-workflow.md - Development rules:
./.claude/workflows/development-rules.md - Orchestration protocols:
./.claude/workflows/orchestration-protocol.md - Documentation management:
./.claude/workflows/documentation-management.md - Git workflow:
- Always merge
devandmainbranches to resolve conflicts before creating PRs - Create PR to
devbranch from other branches to releasebeta - Create PR to
mainbranch fromdevbranch to releasestable
- Always merge
- And other workflows:
./.claude/workflows/* - App release workflow:
./docs/release-workflow.md
IMPORTANT: Analyze the skills catalog and activate the skills that are needed for the task during the process.
IMPORTANT: You must follow strictly the development rules in ./.claude/workflows/development-rules.md file.
IMPORTANT: Before you plan or proceed any implementation, always read the ./README.md file first to get context.
IMPORTANT: Sacrifice grammar for the sake of concision when writing reports.
IMPORTANT: In reports, list any unresolved questions at the end, if any.
Python Scripts (Skills)
When running Python scripts from .claude/skills/, use the venv Python interpreter:
- Linux/macOS:
.claude/skills/.venv/bin/python3 scripts/xxx.py - Windows:
.claude\skills\.venv\Scripts\python.exe scripts\xxx.py
This ensures packages installed by install.sh (google-genai, pypdf, etc.) are available.
Documentation Management
We keep all important docs in ./docs folder and keep updating them, structure like below:
./docs
├── project-overview-pdr.md
├── code-standards.md
├── codebase-summary.md
├── design-guidelines.md
├── deployment-guide.md
├── system-architecture.md
├── release-workflow.md
└── project-roadmap.mdIMPORTANT: MUST READ and MUST COMPLY all INSTRUCTIONS in project ./CLAUDE.md, especially WORKFLOWS section is CRITICALLY IMPORTANT, this rule is MANDATORY. NON-NEGOTIABLE. NO EXCEPTIONS. MUST REMEMBER AT ALL TIMES!!!
In this repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

