safe-principles
Skill0 starsChanged 4 months agoNo licenceView on GitHub
ALWAYS-ON. Core SAFe agent workflow principles. Use on EVERY task. Before any code: (1) SEARCH FIRST — find existing patterns, similar features, past specs in the codebase. (2) PATTERN DISCOVERY — check patterns_library/, search components/ and app/ for reusable implementations. Create new patterns only when nothing exists. (3) EXIT STATES — every phase ends with clear exit: Developer→"Ready for QAS", QAS→"Approved for RTE", RTE→"Ready for HITL". (4) QUALITY GATES — Stop-the-Line: no Acceptance Criteria = no work. QAS gate: no approval = no merge. Security gate: RLS violations block everything. (5) EVIDENCE-BASED — all work validated with tests, session IDs, and demo scripts. When asked to build, fix, review, or plan anything, apply these principles first. Triggers: "implement", "build", "create", "fix", "develop", "review", "plan", "code", "feature", "bug", "task", "story".
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.
In this repository30 other files it gives its agents.
- agent-coordinationSkill
- api-patternsSkill
- confluence-docsSkill
- deployment-sopSkill
- frontend-patternsSkill
- git-advancedSkill
- linear-sopSkill
- migration-patternsSkill
- orchestration-patternsSkill
- pattern-discoverySkill
- release-patternsSkill
- rls-patternsSkill
- safe-be-developerSkill
- safe-bsaSkill
- safe-data-engineerSkill
- safe-data-provisioningSkill
- safe-fe-developerSkill
- safe-qasSkill
- safe-rteSkill
- safe-security-engineerSkill
- safe-system-architectSkill
- safe-tdmSkill
- safe-tech-writerSkill
- safe-git-workflowSkill
- safe-workflowSkill
- security-auditSkill
- spec-creationSkill
- stripe-patternsSkill
- team-coordinationSkill
- testing-patternsSkill
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.