Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package.
Generate application code from a user-reviewed REASONS spec — Profile A (layered FastAPI/SQLAlchemy) or B (ES modules + SRI CDN). Trigger: materialising a signed-off spec as code.
Propagate a REASONS spec change into existing code — diff old vs active spec, classify each change, apply with per-change confirmation. Trigger: code must follow an edited spec.
Package a finished REASONS project for IT review — verify a READY self-review, write a handoff README (versions, install/run/test, TODOs), optional clean ZIP. Trigger: app ready for IT.
Scaffold the project layout for the spec's app profile (A=Python/FastAPI · B=HTML+JS). Trigger: starting a new app in sdd.schema: reasons mode, after the profile is chosen.
Migrate a legacy non-Git SDD workspace (vN filenames + sdddocs/) to the unified Git-based model. Trigger: adopting this generator on a repo built with standalone, pre-Git SDD plugins.
Pick the app profile (A=Python / B=HTML+JS) via a plain-language decision tree and set the spec flags. Trigger: starting a new app in sdd.schema: reasons mode, or when the profile is undecided.
Recover a draft REASONS spec from an existing codebase that arrived without one (or whose spec drifted). Trigger: auditing code that lacks a current spec (reviewer/IT side).
Run the full pre-handoff validation gauntlet (lint, types, tests, coverage, security, SDD-trail consistency) and emit a PASS/FAIL report citing rule IDs. Trigger: self-check before handoff.
Guided conversational interview that turns plain-language needs into a valid REASONS spec (8 sections, closed frontmatter). Trigger: creating a new spec in sdd.schema: reasons mode.
Review and edit a REASONS spec and drive its status lifecycle (draft → user-reviewed → it-approved → implemented → retired) with sign-off gates. Trigger: revising a spec or signing it off.
SPDD code→prompt sync — fold non-behavioural code changes back into the REASONS Canvas and report spec↔code drift. Propose-and-review, never auto-apply. Trigger: code was refactored/fixed and the spec must catch up, or to check drift.
Generate the test suite from the spec's §5 Tests blocks — Profile A pytest (70% coverage, TECH-A-013) or Profile B smoke checklist. Trigger: after code generation.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
Odoo 18 development reference for Python models and ORM (search, domain, readgroup, compute fields), XML/CSV data and views, OWL/JS client code, QWeb reports, security (ACL, record rules, groups), cron and server actions, migrations and module upgrades, tests, i18n, and performance. Use this skill whenever work…
Review Odoo code for correctness, security, performance, and version-specific standards (Odoo 17, 18, or 19). Use when reviewing Odoo modules, diffs, or pull requests; produce a scored report with weighted criteria.
Trace Odoo code execution flow from entry point to end. Use proactively when planning tasks, reviewing code, or understanding how features work end-to-end. Follows all function calls, method overrides, inheritance chains, and callbacks without missing any execution path.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: