From authoring
Guides authoring .claude/rules/*.md files for auto-applied constraints scoped by file patterns. Use when creating or updating rules for code conventions and quality standards.
npx claudepluginhub crouton-labs/crouton-kit --plugin authoringThis skill uses the workspace's default tool permissions.
Rules are constraints Claude follows automatically when working with matching files. They live in `.claude/rules/` or a plugin's `rules/` directory.
Implements Playwright E2E testing patterns: Page Object Model, test organization, configuration, reporters, artifacts, and CI/CD integration for stable suites.
Guides Next.js 16+ Turbopack for faster dev via incremental bundling, FS caching, and HMR; covers webpack comparison, bundle analysis, and production builds.
Discovers and evaluates Laravel packages via LaraPlugins.io MCP. Searches by keyword/feature, filters by health score, Laravel/PHP compatibility; fetches details, metrics, and version history.
Rules are constraints Claude follows automatically when working with matching files. They live in .claude/rules/ or a plugin's rules/ directory.
---
paths:
- "src/api/**/*.ts"
- "**/*.test.ts"
---
Declarative constraints here.
**/*.ts — all TypeScript filessrc/**/* — everything under src/{src,lib}/**/*.ts — multiple directoriespaths entirely for rules that apply everywhereRules without paths load every session. Rules with paths only load when Claude works with matching files.
Be declarative — state what should/shouldn't be done, not step-by-step procedures.
Be specific — "Use 2-space indentation" not "format properly."
Skip the obvious — don't restate best practices Claude already knows. Only specify what's unique to your project.
One topic per file — testing.md, security.md, not everything.md. Organize with subdirectories for grouping.
Provide alternatives — never write "Don't do X" without saying what to do instead.
paths)