infer-design-patterns-from-code

Infer the design-patterns catalogue (architecture/design-patterns.yaml) from scan-index.json during /codify by mapping naming suffixes, framework idioms, and layered directory trees to named patterns — each scoped as system/layer/component/cross-cutting, cited to a driver, with alternatives considered and source_type tagged. Called by tech-architect after logical-architecture and physical-architecture proposals exist.

Ir a la instalación

Repositorio: kapilvirenahuja/garura
Última actividad en el origen: 3 de julio de 2026 a las 06:46
Idioma detectado de SKILL.md: inglés
Estrellas: 3
Forks: 0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/kapilvirenahuja/garura --skill infer-design-patterns-from-code

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

install-garura

Install Garura into a target project or repository so its skills, agents, and plays become discoverable by a host coding tool — Claude Code or the OpenAI Codex CLI. Reads this garura checkout's core/components and runs a per-tool ADAPTER that lays them down in the host's native shape: for claude, .claude/ skills + agents with model tiers resolved to Claude models; for codex, .agents/skills Agent Skills plus AGENTS.md and ~/.codex model/sandbox/approval profiles. Always writes a .garura/ tooling tree (config + STM scaffold) and copies shared memory to the machine-global ~/.garura, and records an install manifest so uninstall-garura can reverse exactly what was placed. Use when the user wants to install, set up, bootstrap, add, or enable Garura in another folder or repo for claude or codex — "install garura into X", "set up garura in this repo for codex", "bootstrap garura", "make codex see the garura skills". Takes the target path, an optional --tool, and an optional --scope (full = everything, the default; ha

2026-07-21

play-creator

Compile a deterministic "play" (a multi-step, gated workflow recipe) from an intent. Interviews for the intent triple, generates the expectation, identifies the skills, scripts, and agents the play needs, selects a workflow structure, generates evals, and emits a compiled play (a SKILL.md plus bundled scripts for its mechanical work). Use this whenever the user wants to create, build, compile, or review a play — or says "create a play", "new play", "compile this into a play", "play-creator", "turn this intent into a play", or "review my play for gaps" — even if they don't say the word "play" explicitly but are describing a repeatable, multi-step, checkpoint-gated workflow they want captured as a runnable recipe.

2026-07-21

play-editor

Modify an existing compiled play — change its goal, a constraint, a failure condition, a success scenario, a step, the workflow shape, or the agents/skills it uses — by editing the play's ICE source and recompiling, never by hand-patching the output into disagreement with its intent. This is the companion to play-creator (which makes new plays). Use this whenever the user wants to edit, change, modify, update, tweak, extend, or fix an existing play — or says "edit the play", "change this play", "add a constraint to the play", "the play needs a new failure condition / step / scenario", "play-editor", or "recompile the play after I changed its intent" — even if they don't say "play" outright but are clearly reshaping a workflow recipe that already exists.

2026-07-21

Ver todos los de este repositorio

infer-design-patterns-from-code

Called by tech-architect during /codify, after logical-architecture and physical-architecture proposals have been written. Produces {stm_base}/{issue}/evidence/codify/proposals/architecture/design-patterns.yaml.

Purpose

Brownfield projects already encode their design patterns in directory layout, naming conventions, and framework idioms — a Repository-suffix cluster proves the Repository pattern; a src/domain + src/application + src/infrastructure tree proves Hexagonal / Clean Architecture; a queue dep plus listener files prove Pub/Sub. The /codify bootstrap must lift that knowledge out of code so the pattern catalogue matches reality before a human edits it.

This skill reads scan-index.json plus the sibling logical and physical architecture proposals, applies a deterministic signal → pattern mapping table, scopes every detected pattern (system / layer / component / cross-cutting), cites a concrete driver, lists ≥ 1 alternative, and tags every entry source_type: inferred_from_code.

Tier-1 inference. learning_category: arch. sub_category: patterns.

Input

Receive from tech-architect via JSON contract. All paths absolute.

Field

Required

Description

scan_index_path

yes

scan-index.json produced by scan.py.

stm_base

yes

STM root (stm.base-path in .garura/core/config.yaml).

issue

yes

Issue number (STM namespace).

output_path

yes

{stm_base}/{issue}/evidence/codify/proposals/architecture/design-patterns.yaml.

decision_manifest_path

yes

{…}/architecture/decision-manifest-infer-design-patterns.yaml.

resolution_trace_path

yes

{…}/architecture/resolution-trace-infer-design-patterns.yaml.

infer-design-patterns-from-code

Purpose

Tier-1 inference. learning_category: arch. sub_category: patterns.

Input

Receive from tech-architect via JSON contract. All paths absolute.

Field

Required

Description

scan_index_path

yes

scan-index.json produced by scan.py.

stm_base

yes

STM root (stm.base-path in .garura/core/config.yaml).

issue

yes

Issue number (STM namespace).

output_path

yes

{stm_base}/{issue}/evidence/codify/proposals/architecture/design-patterns.yaml.

decision_manifest_path

yes

{…}/architecture/decision-manifest-infer-design-patterns.yaml.

resolution_trace_path

yes

{…}/architecture/resolution-trace-infer-design-patterns.yaml.

Signal source

Signal value

Pattern inferred

Default scope