exec-architecture
Skill1 starsChanged 28 days agoMITView on GitHub
Execution skill loaded when making structural decisions, creating new modules, or defining component boundaries.
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-refactoringSkill
- exec-repo-patternsSkill
- 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
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
When adding a new feature or module, avoid jumping straight into implementation.
- Distinctive: line 9
Placement: Should this be a generic utility, a specific domain service, or a UI component?
- Distinctive: line 12
Trade-offs: Before writing the final code, present 2 viable design options (e.g., interface vs.
≈ “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
Architecture Execution Strategy
When adding a new feature or module, avoid jumping straight into implementation. Instead, evaluate the architectural placement:
- Placement: Should this be a generic utility, a specific domain service, or a UI component?
- Extensibility: Are you extending an existing abstraction or creating a new one? If creating a new one, is it truly necessary?
- Coupling: How tightly coupled will this new code be to existing modules? Aim for loose coupling and high cohesion.
- Trade-offs: Before writing the final code, present 2 viable design options (e.g., interface vs. abstract class, or stateful vs. stateless) and state the trade-offs.
Rule of Thumb: Many coding mistakes are architectural. Ask yourself if the proposed structure will scale with the project before writing the implementation.
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.