Design and review REST APIs with consistent conventions, URL structure, status codes, and error formats. Use when creating endpoints, auditing an existing API for consistency or quality, or settling team disagreements on API conventions.
Perform a structured code review — what to check, in what order, and how to formulate constructive feedback. Use before merging a PR, on demand for a specific file or module, or for end-of-sprint quality audits.
Apply file structure, naming, and code organization rules to produce clean, consistent, maintainable code. Use when writing new code, refactoring, creating a new module or component, or as a complement to code review.
Prepare, execute, and validate a deployment — pre-flight checks, release procedure, post-deploy verification. Use before production releases, when setting up CI/CD, after a critical fix that must ship quickly, or to document the deployment procedure for a new project.
Document code, modules, and learnings — what to document, in what format, and when to update the project memory. Use after writing or modifying a public function, at sprint end to consolidate learnings into the cortex, when creating a module, or when writing or updating an issue.
Apply Lytos Git conventions — branch naming, commit message format, merge workflow, and collaboration rules. Use when creating a branch, committing changes, opening a PR, or resolving a workflow conflict or question.
Identify vulnerabilities, apply secure coding patterns, and enforce security best practices across any language. Use when writing code that handles user input, authentication, or authorization; during code review for OWASP Top 10 issues; when adding dependencies; or when configuring servers, APIs, or deployment…
Write and review tests — unit, integration, and E2E — following the Testing Trophy model. Use after writing a feature, after fixing a bug (regression test required), during refactoring (existing tests must continue to pass), or during a quality audit to check overall coverage.