Menu
Guidance on how code should be written in this repo. If you add or modify code, load this skill.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
This skill described the process to follow when asking the user questions. If you will ask the user questions in any way, load this skill first.
Work instruction for concluding a feature. If you helping with development in ANY way, you MUST load this skill.
This skill defines the process to follow for developing new features. Load this skill if you are tasked with changing anything in the `src/myteam/` directory.
Load this skill only when asked to by the user.
This skill describes our philosophy towards the kinds of tests we write and the framework used to implement tests. If you need to read, add, or modify tests, load this skill.
Local development-workflow guidance for asking the user questions. Load this skill before any development-workflow role asks the user questions or requests approval.
| name | Framework-oriented Design |
| description | Guidance on how code should be written in this repo. If you add or modify code, load this skill. |
An application is a combination of framework and business logic.
We seek to separate framework code for business logic code.
Framework refers to the internal, helper code that supports the primary API of the application, as well as the conventions and patterns used in the codebase to create consistency and structure.
When preparing to implement a feature, understand the existing framework:
Then consider: should changes be made to the framework to support the new feature?
The business logic of the new feature should fit cleanly within the framework. Therefore, a change to the framework may be needed first, followed by a change to the business logic.
If a change to the framework is needed, refactor the code accordingly without adding any new behavior.
Guidance:
