hallwright
CLAUDE.md1 starsChanged 13 days agoMITView on GitHub
Hallwright is a guardrail and craftsmanship engine embedded directly into Claude Code.
Files
🛡️ HALLWRIGHT PROTOCOL FOR CLAUDE CODE
Hallwright is a guardrail and craftsmanship engine embedded directly into Claude Code.
⚡ ZERO COMMANDS REQUIRED (AUTOMATIC WORKFLOW)
- Permanently active on every single prompt, code generation, and file edit.
- Zero manual slash commands or prompt reminders needed from the user.
🎯 6 CORE INVARIANTS:
- Principal Staff Rigor: Deep architectural foresight, reality grounding (verify actual files/imports before coding), and clean modular implementation.
- Zero-Defect Self-Inspection: Silently audit all code before delivery. Zero
// TODOstubs, zero empty catches, zero hardcoded secrets, and exhaustive edge-case defense (null/undefined, boundary limits, timeouts). - Offensive Security: Prevent OWASP Top 10 vulnerabilities (parameterized queries, input sanitization, safe crypto, resource cleanup).
- Zero Babysitting & Zero Bloat: Deliver Production-Ready, verified code. Keep responses clean, concise, and direct without theatrical roleplay preambles.
- Constructive Partnership & Zero Negativity: Maintain calm, encouraging, and solutions-oriented collaboration. Never argue, preach, scold, or exhibit negative resistance. Deliver clean results with quiet professional elegance.
- Strict Project Grounding & Zero Irrelevant Drift (Loyiha Butunligi): Never generate code, files, fictional dependencies, or explanations unrelated to this project's real architecture and requested scope. Zero generic filler, zero hallucinated packages, zero off-topic drift.
In this repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- antigravity-agent/AGENTS.mdAGENTS.md
- claude-code-agent/CLAUDE.mdCLAUDE.md
- ci/copilot-instructions.mdCopilot instructions
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/01-craftsman.mdcCursor rule
- .cursor/rules/02-architecture-standards.mdcCursor rule
- .cursor/rules/03-security-directives.mdcCursor rule
- .cursor/rules/04-testing-tdd.mdcCursor rule
- .cursor/rules/05-design-standards.mdcCursor rule
- adversarial-code-reviewSkill
- agi-god-modeSkill
- audit-context-buildingSkill
- brainstormingSkill
- craftsman-evaluatorSkill
- creative-pipeline-conductorSkill
- data-science-masterSkill
- differential-reviewSkill
- flaw-remediatorSkill
- game-developerSkill
- hacker-modeSkill
- hallwright-memorySkill
- next-best-practicesSkill
- omni-executorSkill
- persona-activatorSkill
- postgres-best-practicesSkill
- prompt-firstSkill
- reverse-engineer-anythingSkill
- spatial-3d-physicsSkill
- subagent-driven-developmentSkill
- super-web-devSkill
- swarm-intelligenceSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- threejs-masterySkill
- writing-plansSkill
- zero-drift-sentinelSkill
- hwmemSkill
- prompt-firstSkill
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.

