ak

Plugin ak from marketplace access-modernization-kit in tuanvtanrakutei/access-modernization-kit. Commands read from the repo's manifest — 29 days ago.

Skills (11)

• bootstrap-project

  Set up a brand-new modernization project - copy the template documents into a target repo's docs directory, and seed Screens_Registry.md from a five-phase run's Phase 2 inventory when one exists. Trigger when the user wants to start a new Access-family modernization project, bootstrap a project, or

• code-screen

  Implement one screen from its existing, already-frozen screen plan - backend then frontend (Stages 3a-3b). Refuses to start unless Stages 1-2 already produced a two-contract screen plan with a populated gap matrix. Trigger when the user explicitly wants just the coding stage for a screen that alread

• dev-stack

  Bring a modernization project's Docker stack up, check it, or stop it - backend, frontend and a local development database, with migrations applied. Trigger when the user wants to start, run, check or stop the project locally, or a check needs the stack. Examples: \"/ak:dev-stack up\", \"/ak:dev-sta

• investigate

  Analyze Microsoft Access VBA applications and MDB/ACCDB/ADP projects connected to SQL Server through a mandatory five-phase, evidence-backed legacy-system investigation with Access extraction, deterministic module planning, and provider-neutral multi-agent orchestration. Use when an agent must packa

• modernize-screen

  Run the end-to-end legacy Access modernization pipeline for one screen or several in parallel — computed scope, screen plan, backend coding, frontend coding, tests, and review. Trigger when the user wants to implement, refresh, test, or review a screen of a legacy Access application being rebuilt as

• plan-screen

  Run Stages 1 and 2 only for one screen - the computed scope and the screen plan - without touching code. Trigger when the user explicitly wants just the planning and documentation stages for a screen, not full implementation - modernize-screen already covers straight through implementation, so use t

• review-screen

  Review one screen against every upstream artifact and record a verdict (Stage 5). Reviews whatever upstream artifacts exist and says what's missing, rather than refusing outright. Trigger when the user explicitly wants a review or a verdict for one screen. Examples: \"/ak:review-screen OrderEntry\",

• screen-status

  Read-only status for one screen or the whole registry - artifacts present, track status, open findings. Writes nothing, always safe to run. Trigger when the user wants to check where a screen or the whole project stands without starting any work. Examples: \"/ak:screen-status OrderEntry\", \"screen-

• test-screen

  Write and run the tests for one screen - backend suite then frontend end-to-end (Stages 4a-4b) - and close the stage with the evidence and gate G4: which rules the tests back, whether they can fail, whether the output matches the legacy output. Refuses to start unless a coding record already exists

• triage-suite

  Work out what is actually wrong with a failing test suite by grouping failures by error signature instead of by file, so a wall of red resolves into a few root causes. Trigger when a suite is red and the cause is unclear, when there are more failures than anyone wants to read one at a time, before d

• validate-docs

  Check a bootstrapped modernization project's documentation set for defects a reader will not notice — unfilled config keys, unresolved placeholders, dangling document references, malformed or duplicated issue rows, issue numbers cited by code with no row, resolved rows citing files that no longer ex

Hooks (1)

• PostToolUse

  python "${CLAUDE_PLUGIN_ROOT}/hooks/scope_sensor.py"

Similar plugins