repo `ai-shortfilm-prompts` (MIT, same author). The upstream `SKILL.md` is an
**interactive** Claude Code skill (it asks via AskUserQuestion, `Read`s template files); AO steps
have no tools
demo extension at ~/.config/muxy/extensions to the user.
- Prefix the demo extensions with `demo-*`
## CodeReview
- Review changes against the stated PR, issue, or task. Start with the diff, directly affected
plugins/arckit-claude/hooks/README.md).** [`plugins/arckit-claude/docs/ENFORCEMENT.md`](plugins/arckit-claude/docs/ENFORCEMENT.md) is the three-tier statement of what the hooks enforce in code, what is only asked of the model, and what the deploying organisation owns — a change
translations in the same commit
- Translations can be machine-generated but should be reviewed for obvious errors
## Versioning
- Follow [Semantic Versioning](https://semver.org/)
- Sync version across: `package.json`, `.claude-plugin
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
If the user's prompt starts with “EP:”, then the user wants
work autonomously in parallel, communicate with each other, create and manage their own tasks, reviewcode, and collaborate across teams. You manage everything through a kanban board — like
Creation & Optimization Skill
## Project Overview
This repository contains **Claude Blog**, a Tier 4 Claude Code skill for blog content
creation, optimization, and management. It follows the Agent Skills open standard
rules live in `docs/BACKTESTING_ARCHITECTURE.md` under "RULE #1". Read it before touching any data-fetching code.
## Quick Start
**First, read these files:**
1. `docs/BACKTESTING_ARCHITECTURE.md` - Understand the backtesting data flow
existing pages
- Include both basic and advanced use cases
- Language tags on all code blocks
- Alt text on all images
- Relative paths for internal links
## Common mistakes to avoid
- **Inconsistent
browsing.
- Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context.
- After modifying code, run `graphify update .` to keep the graph current
module named `nudge_builtins` (not `builtins`) because the stdlib `builtins` is loaded before user code and would permanently shadow a local `builtins.py`; handlers/matchers referenced by allowlisted string name only
each exists, and the
measurements behind them. It is loaded automatically by Claude Code.
**Contributors: start with `CONTRIBUTING.md`** — the short version (setup, boundaries, house rules,
testing habits). This file
description" --body "Closes # "
```
4. **Before merging**, ensure:
- CI pipeline passes (all checks green)
- Code has been reviewed if required
- No merge conflicts with `main`
**IMPORTANT:** Never push directly to `main
that take required parameters or handle workspace state. |
| [NAMING_CONVENTIONS.md](./docs/NAMING_CONVENTIONS.md) | Designing wire protocols, sync code, or SQL schemas. |
| [AI_PROVIDER_TYPES.md](./docs/AI_PROVIDER_TYPES.md) | Working on AI integration, adding providers, or modifying model selection
Code Local Notes
- `.claude/settings.json` blocks direct edits to lockfiles; use npm or pnpm commands instead.
- `.claude/settings.json` also auto-runs SDK lint autofix after TypeScript file edits.
- If you need reviewer
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.