align
Skill5 starsChanged 7 months agoMITView on GitHub
Use when the user needs scope alignment, shared language, or docs clarity before or between gated lanes.
16 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- dimsedra/skillstheir own version, first seen Nov 8, 2026
- devjiwonchoi/skillstheir own version, first seen Nov 8, 2026
- KerberosClaw/kc_ai_skillstheir own version, first seen Nov 1, 2026
- lgy1027/specflow-agent-packtheir own version, first seen Nov 1, 2026
- hmmhmmhm/aligns.mdtheir own version, first seen Oct 17, 2026
- hmmhmmhm/align.mdtheir own version, first seen Oct 15, 2026
Used with
Projects with it also use blueprint, research and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
WordPressSkillblueprint
Use when the deliverable is WordPress Playground Blueprint JSON or a Blueprint bundle, including creating, editing, reviewing, validating schema keys, choosing steps/resources, and debugging Blueprint files. For only running or sharing a Playground environment, use wp-playground.
Also in 3 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- JustineDevs/premortem★ 2100% same
Wrote their own version · 15
- ambient-code/platform★ 131same name
- KerberosClaw/kc_ai_skills★ 79same name
- samirpatil2000/skills★ 17same name
- hmmhmmhm/align.md★ 9same name
- hmmhmmhm/aligns.md★ 9same name
- HaipingShi/coderail★ 8same name
- lgy1027/specflow-agent-pack★ 4same name
- devjiwonchoi/skills★ 2same name
- dimsedra/skills★ 2same name
- Carefree-1991/claude-skills★ 1same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill inside Codex when the problem is ambiguity, drift, or mismatched language rather than missing implementation.
- Distinctive: line 22
Prefer tightening existing artifacts over inventing parallel docs.
- Very specific: line 23
Keep terminology Meta-Architect-native for user-facing surfaces.
- Very specific: line 24
Use references/shared-language.md for naming, taxonomy, and docs-clarity patterns.
- Distinctive: line 36
Every recommendation names its evidence or labels the gap as unknown.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Align
Use this skill inside Codex when the problem is ambiguity, drift, or mismatched language rather than missing implementation. align is a non-gating helper skill.
Output
Produce:
- current ambiguity or mismatch
- normalized terminology
- scope boundary and exclusions
- acceptance checks or rewritten prompts
- exact next trigger, usually
$maestroor the lane that owns the next decision
Rules
- Align language and scope without creating a new release gate.
- Prefer tightening existing artifacts over inventing parallel docs.
- Keep terminology Meta-Architect-native for user-facing surfaces.
- Use
references/shared-language.mdfor naming, taxonomy, and docs-clarity patterns.
Procedure
- Identify the exact artifact, decision, lane, and owner currently in scope.
- Separate facts already verified from assumptions, requests, and unresolved choices.
- Normalize conflicting terms into one product-native vocabulary and record exclusions.
- Rewrite the smallest useful prompt, acceptance check, or handoff note.
- Return the next owner and trigger; do not silently advance a gated lane.
Quality bar
- Every recommendation names its evidence or labels the gap as unknown.
- Scope changes are explicit and reversible.
- The result is actionable by one next owner, not a broad list of suggestions.
Example
For “the release flow is drifting,” distinguish the package version, Git tag, release workflow, and published artifact before proposing a correction. Route implementation to the owning lane after the terminology and boundary are stable.
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.