exec-repo-patterns
Skill1 starsChanged 28 days agoMITView on GitHub
Execution skill loaded to adapt code generation to the existing repository architecture, style, and conventions.
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-refactoringSkill
- exec-securitySkill
- exec-testingSkill
- exec-ui-uxSkill
- exec-verificationSkill
- tech-dockerSkill
- tech-flutterSkill
- tech-goSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nextjsSkill
- tech-nodeSkill
- tech-postgresSkill
- tech-pythonSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-tailwindSkill
- tech-typescriptSkill
- tech-vueSkill
- linear-spanks-gitSkill
- linear-spanksSkill
- linear-workflowSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Before implementation, establish the following facts for the affected area.
≈ “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
Repository Patterns Strategy
Before implementation, establish the following facts for the affected area. Reuse observations already verified against relevant source hashes, worktree identity, contracts, and toolchain; inspect only missing or changed evidence. A tiny edit does not require a new repository-wide exploration:
- Architecture Layout: Where does business logic live vs. UI logic vs. data access?
- Naming Conventions: Are files
kebab-case,camelCase, orPascalCase? Are interfaces prefixed withI? - Error Handling: How does this codebase handle exceptions? Does it return Error objects, throw exceptions, or use a specific logging service?
- Testing: What testing library is used? Where are tests located (
__tests__, co-located, etc.)?
CRITICAL RULE: Generate code that feels native to this repository. Do not introduce a new paradigm, pattern, or preferred library unless explicitly requested. Mimic the existing code structure.
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.