Build & Development Commands

• Use npx commands for toolchain tasks (e.g., npx -y <tool>)
• Prefer local CLI tools over global installations
• All dev commands must be runnable via MCP blocks or Titan CLI orchestration
• Use .env for tokenized CLI credentials (autoinjected by Jarvis)

Testing Guidelines

• All code must include a corresponding test block if logic is non-trivial
• Use jest, vitest, or pytest depending on the language context
• Test coverage minimum: 80%
• Include negative tests and failure cases
• All MCP actions must return a status code and stdout/stderr

Code Style & Guidelines

• Enforce Prettier + ESLint on save (autofix on commit)
• Use camelCase for variables, PascalCase for types and components
• Auto-generate types from OpenAPI, GraphQL, or schema tools
• Avoid magic strings — use constants or enums

Documentation Guidelines

• Every block or command must include inline comments for LLM context parsing

• Use README.md and IMPROVEMENTS.md for manual + change logs

• Public blocks must include:

  • Description
  • Usage example
  • Inputs/Outputs (arguments)

• Diagrams or call graphs must be included for workflows with >3 steps