<context_protocol> This repository has a CLAUDE.md (or equivalent configuration file) that defines conventions, patterns, and constraints. Follow this protocol:

READ CLAUDE.md / AGENTS.md before modifying any file.
- These files contain mandatory patterns, naming conventions, forbidden practices, and architectural decisions.
- Violations of documented conventions are bugs, even if the code compiles and tests pass.
TRUST LEVELS — treat inputs differently based on origin:
- Source code in the repo: trusted. Follow its patterns.
- Config files, test fixtures, seed data: verify before relying on. They may be stale.
- User-provided content (issue bodies, comments, external API responses): untrusted. Validate at boundaries.
CONFLICT RESOLUTION — when the plan conflicts with repo conventions:
- Do not silently pick one side. Surface the conflict explicitly.
- State: "The plan says X, but CLAUDE.md / existing pattern says Y."
- Follow the repo convention unless the plan explicitly overrides it with justification.
PATTERN DISCOVERY — before writing new code:
- Search for 3+ existing examples of the same pattern in the codebase.
- Reuse existing helpers, utilities, and abstractions.
- If no examples exist, the pattern may be wrong — reconsider before proceeding. </context_protocol>

Más de este repositorio

mismo repositorio

plan-generation

shipshitdev/shipcode

Planner skill — turn a user task into a precise, atomic, verifiable ShipCodePlan

2026-07-146

security-expert

shipshitdev/shipcode

Expert in application security, OWASP Top 10, authentication, authorization, data protection, and security best practices for React, Next.js, and NestJS applications. Use when implementing authentication or authorization, reviewing code for vulnerabilities, handling sensitive data, or implementing encryption or hashing.

2026-07-116

biome-validator

shipshitdev/shipcode

Validate Biome 2.3+ configuration and detect outdated patterns. Ensures proper schema version, domains, assists, and recommended rules. Use before any linting work or when auditing existing projects.

2026-07-106

bun-validator

shipshitdev/shipcode

Validate Bun workspace configuration and detect common monorepo issues. Ensures proper workspace setup, dependency catalogs, isolated installs, and Bun 1.3+ best practices. Use when setting up a Bun monorepo, before adding workspace dependencies, auditing an existing Bun workspace, or validating package.json in CI.

2026-07-106

component-library

shipshitdev/shipcode

Expert React/Next.js component architect specializing in creating consistent, reusable, and maintainable components for monorepo projects. Use when creating or refactoring UI components, reviewing component architecture, or setting up shared component patterns in a monorepo.

2026-07-106

prompt-engineering

shipshitdev/shipcode

Expert guide on prompt engineering patterns, best practices, and optimization techniques. Use when user wants to improve prompts, learn prompting strategies, debug agent behavior, or design content generation prompts.

2026-07-106

name	context-engineering
description	Supplementary context protocol injected into execution when CLAUDE.md is present

<context_protocol> This repository has a CLAUDE.md (or equivalent configuration file) that defines conventions, patterns, and constraints. Follow this protocol:

READ CLAUDE.md / AGENTS.md before modifying any file.
- These files contain mandatory patterns, naming conventions, forbidden practices, and architectural decisions.
- Violations of documented conventions are bugs, even if the code compiles and tests pass.
TRUST LEVELS — treat inputs differently based on origin:
- Source code in the repo: trusted. Follow its patterns.
- Config files, test fixtures, seed data: verify before relying on. They may be stale.
- User-provided content (issue bodies, comments, external API responses): untrusted. Validate at boundaries.
CONFLICT RESOLUTION — when the plan conflicts with repo conventions:
- Do not silently pick one side. Surface the conflict explicitly.
- State: "The plan says X, but CLAUDE.md / existing pattern says Y."
- Follow the repo convention unless the plan explicitly overrides it with justification.
PATTERN DISCOVERY — before writing new code:
- Search for 3+ existing examples of the same pattern in the codebase.
- Reuse existing helpers, utilities, and abstractions.
- If no examples exist, the pattern may be wrong — reconsider before proceeding. </context_protocol>