Enforce SOLID principles, guard-clause style, function size limits, and intention-revealing naming across all languages. Use when refactoring for readability, applying clean-code patterns, reviewing naming conventions, or reducing function complexity. (triggers: **/*.ts, **/*.tsx, **/*.go, **/*.dart, **/*.java, **/*.kt, **/*.swift, **/*.py, solid, kiss, dry, yagni, naming, conventions, refactor, clean code)
RESTful API design best practices and conventions guide
Create a pull request for EmbodiChain following the project's PR template and conventions
General conventions when creating an application design
Use token-efficient CLI patterns instead of verbose MCP output when direct shell tools are enough. Provides JSON or compact-output conventions for gh, mgrep, psql, and similar tools.
RESTful API design conventions including endpoint naming, HTTP methods, status codes, pagination, error handling, and versioning patterns. Use when designing APIs, creating endpoints, or reviewing API contracts.
REST API design conventions, error shapes, versioning, and pagination patterns. Use when designing or reviewing any HTTP API.
This skill should be used when the user asks about "nf-core conventions", "strict syntax", "naming conventions", "output patterns", "coding style", "best practices", "parameter naming", "channel naming", "process labels", or how to structure nf-core code correctly. Covers strict syntax rules (Q2 2026 deadline), output glob patterns, and naming conventions.
Core conventions and patterns for this codebase
Use when writing, reviewing, or validating Claude Code plugin artifacts — check frontmatter schemas, hook event names, naming conventions, prompt structure, or reference syntax. Loaded by the NLPM scorer and checker agents for schema validation.
Creates a commit: detects conventions, stages intentionally, writes a clear subject, add a concise body when useful, and commits.
Naming conventions, code style rules, and quality examples for all code written by the agent.
