Menu
Use when wanting minimal project rules without design docs or implementation plans — just CLAUDE.md and AGENTS.md
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
Use when explaining unfamiliar concepts, architectures, bugs, or implementation patterns. Focus on mental models, why the pattern exists, and transfer to other contexts instead of surface-level code explanation.
Write responses in a thoughtful, technically confident, collaborative engineering tone suitable for GitHub, Discord, OSS discussions, reviews, chats, and maintainer conversations.
Use when the user wants to understand existing code — what it does, why it exists, and how to recall it later. Not for teaching during implementation (use mentor-mode). Use when the user asks "what does this file do", "explain this code", or points at code they don't understand.
Use when adding project structure and rules to an existing codebase that has no CLAUDE.md or AGENTS.md
Use when starting a brand new project from scratch and needing project structure, rules, and documentation files generated
| name | just-rules |
| description | Use when wanting minimal project rules without design docs or implementation plans — just CLAUDE.md and AGENTS.md |
Creates CLAUDE.md and AGENTS.md only. No docs/, no plans, no design specs.
Project context file. Keep under 60 lines.
Must include:
@AGENTS.md — import for all coding conventionsAll coding rules. Keep under 80 lines.
Must include:
# AGENTS.md
## Working Rules
- EXPLAIN FIRST — explain WHAT and WHY before writing code
- ONE LOGICAL UNIT — one unit of work per response, one commit per unit
- COMMIT AFTER EACH FEATURE
- ANSWER QUESTIONS — pause and explain when asked
- DRY — extract shared logic
## Code Style
- Comments explain WHY not WHAT, no JSDoc unless public API
- Use CSS variables/tokens, no arbitrary colors
- Use cn() for conditional class merging
- No inline styles, use Tailwind classes
## Git
- Format: feat: one liner description
- One logical change per commit
## Anti-Patterns (Avoid)
- Generic blue/indigo everywhere
- Same border radius on everything
- Gradient backgrounds
- Template nav bars
- Bland "Welcome to..." headings
- Default shadows on all cards
## Prefer Instead
- Asymmetric layouts, mixed border radii
- Dark mode support
- Micro-interactions, skeleton loaders
- Personality over templates