SHARP · FORGE · CRAFT
Three thinking frameworks developed while building Simplifii-OS — a neuroinclusive academic operating system for students with ADHD, dyslexia, other processing differences and marginalised backgrounds. But caters to all.
These frameworks are open. Use them in any Claude Code project.
Claude Code is powerful. But without structure, sessions drift. Diffs get approved without being read. The same bugs recur. Features get built before the foundation is stable. AI output gets trusted without being verified.
These three frameworks enforce fifteen dimensions of discipline simultaneously — applied to every sprint, every diff, every CC prompt.
One line at the top of every CC prompt:
SHARP active. FORGE active. CRAFT active.
Decide what to build and why.
| Letter | Dimension | What it asks |
|---|---|---|
| S | Systems | Does this close a loop or add noise? |
| H | Hallucination guard | Am I approving something I haven't verified exists? |
| A | Architecture | What breaks downstream? |
| R | Root cause | Can I name the exact cause in one sentence? |
| P | Prompt discipline | Do I have gate words and nothing past the first gate? |
SHARP combines: systems thinking, hallucination-reduction discipline, SE engineering lenses, and prompt habit audit into one framework.
Trigger: Say "SHARP active" or "run SHARP on this."
Build it without breaking anything.
| Letter | Dimension | What it enforces |
|---|---|---|
| F | Flow | Break work into steps. Paste one step at a time. |
| O | Origin safety | Clean git before any edit. Tagged backups on fragile surfaces. |
| R | Red first | Failing test before implementation. Always. |
| G | Grain | Design tokens only. No raw hex. Consistent visual language. |
| E | Echo | Read session log first. Write handoff at session end. |
FORGE combines: planning-with-files pattern, TDD discipline, Git worktree safety, frontend design standards, and memory continuity across sessions.
Trigger: Say "FORGE active" or add "FORGE active." to any CC prompt.
Make sure it works for the actual humans who will use it.
| Letter | Dimension | What it checks |
|---|---|---|
| C | Content + SEO | Can people find it? Does it communicate clearly? |
| R | Research memory | Are sprint decisions persisted across sessions? |
| A | Accessibility + UDL 3.0 | WCAG 2.2 AA. Multiple means. Neurodivergent-first. |
| F | Fortify | Security patterns. No PII in telemetry. Dependency audit. |
| T | Teaching + pedagogy | Cognitive load. Retrieval practice. Trauma-informed defaults. |
CRAFT combines: web quality discipline, persistent planning (planning-with-files pattern), WCAG 2.2 AA enforcement, security vulnerability patterns, and UDL 3.0 learning science.
Trigger: Say "CRAFT active" or "CRAFT check on this."
SHARP active. FORGE active. CRAFT active.
SESSION CONSTRAINT: [one task, named precisely]
Log any other issues to BACKLOG. Do not fix outside constraint.
ECHO: Read SESSION_LOG and BACKLOG first.
FLOW plan:
[ ] Step 1: Read and report (no code, wait for confirmation)
[ ] Step 2: Propose (no code, wait for approval)
[ ] Step 3: Implement [file A]
[ ] Step 4: Test
[ ] Step 5: Session end + deploy
STEP 1: READ AND REPORT
Read [exact files]. Report [exact questions].
Do not write anything.
Wait for: "confirmed, proceed with Step 2"
STEP 2: PROPOSE
Show [exact output].
Wait for: "confirmed, proceed with Step 3"
STEP 3: IMPLEMENT
Read [file] immediately before editing.
Show git diff --staged.
Wait for: "looks good, commit [name]"
STEP 4: TEST
Three smoke questions. Run test suite.
STEP 5: SESSION END
Write session log. git push. One deploy.
RULES:
- Read every file immediately before editing
- Show diff before every commit
- Gate words only: "looks good, commit [name]" / "confirmed, proceed"
- Never proceed without the exact gate phrase
- One deploy at end
The most important single discipline in FORGE: CC does not commit, proceed, or execute without seeing one of these exact phrases:
looks good, commit [name]— the only phrase that triggers a commitconfirmed, proceed with Step N— the only phrase that moves forwardlog to BACKLOG as [ID]— the only phrase that defers without pursuing
If CC acts without a gate word, it bypassed a gate. Do not accept it silently.
Copy the skill files to your user-level Claude skills directory:
SKILLS_DIR="$HOME/.claude/skills"
mkdir -p "$SKILLS_DIR/SHARP" && cp SHARP-SKILL.md "$SKILLS_DIR/SHARP/SKILL.md"
mkdir -p "$SKILLS_DIR/FORGE" && cp FORGE-SKILL.md "$SKILLS_DIR/FORGE/SKILL.md"
mkdir -p "$SKILLS_DIR/CRAFT" && cp CRAFT-SKILL.md "$SKILLS_DIR/CRAFT/SKILL.md"
echo "SHARP, FORGE, CRAFT installed"Claude Code loads skill descriptions at startup. When you say "SHARP active" it loads the full framework into context.
I have ADHD and dyslexia. I built Simplifii-OS — seven iterations — for students whose brains work differently. These frameworks emerged from the practical need to keep Claude Code sessions disciplined when your own working memory cannot hold the rules.
The R in CRAFT stands for Research Memory precisely because externalising plans and decisions is not a workaround for ADHD — it is the correct engineering pattern regardless.
The A in CRAFT stands for Accessibility + UDL because when your product's primary user is a neurodivergent student, accessibility is not a compliance checkbox. It is the product.
Aaron Saint-James Founder, Simplifii Pty Ltd MRes Inclusive Education, UNSW Sydney aaron@simplifii.com.au
MIT. Use freely. Attribution appreciated but not required.
If these help you build something better for people who think differently, that is enough.