@ds9-solutions/mcp 0.4.0 → 0.6.0

package/README.md

@@ -32,11 +32,21 @@ No Windows, hosts que não resolvem `npx` usam `"command": "cmd", "args": ["/c",
 | `list_skill_files` / `get_skill_file` | Lista e lê os arquivos complementares de uma skill (`examples/`, `references/`), sob demanda |
 | `list_agents` / `get_agent` | Lista os subagentes e lê o conteúdo de um |
 | `search_guidelines` | Busca um trecho em todas as skills e agentes |
+| `list_presets` | Lista os presets Spec Kit e o comando de instalação (somente leitura; não instala nada) |
 
 Também expõe prompts (`skill-<id>`, `agent-<id>`) e resources (`ds9://skills/<id>`, `ds9://agents/<id>`).
 
 Os arquivos complementares são servidos a partir de um índice em memória: só extensões permitidas, sem links simbólicos, com limite de tamanho e de quantidade, e sem acesso a caminhos arbitrários do disco.
 
+## Presets Spec Kit
+
+Requer o `specify` (>=1.2.1) no PATH e um projeto com `.specify/`. A instalação é feita pelo próprio Spec Kit (`specify preset add --dev`), que mantém o `.registry`:
+
+```bash
+npx -y @ds9-solutions/mcp presets list
+npx -y @ds9-solutions/mcp presets add dart-frog-hexagonal [--priority 10] [--dir <projeto>]
+```
+
 ## Conteúdo
 
 Skills: `dart`, `hex-pattern-dart`, `dart-frog`, `driftorm`, `flutter` e `debugger`.

package/content/presets/dart-frog-exceptions/README.md

@@ -0,0 +1,26 @@
+# Shared exceptions preset
+
+This independent Dart Frog preset defines shared exception responsibilities
+under `lib/common/exception/`: `BusinessException`, `ClientException` and
+`MiddlewareException`. It does not prescribe an HTTP response format, retry
+policy or another preset. Existing behavior and contracts are not changed
+automatically; material conflicts must be presented to the owner.
+
+The three template additions use `prepend` and are visible as Markdown. They
+guide artifact generation and do not enforce code compliance automatically.
+
+## Manual installation
+
+Requires Spec Kit 1.2.1 or later. From the target API repository root, replace
+the example path with the actual location:
+
+```sh
+specify preset add --dev /absolute/path/to/.specify_customs/exceptions
+```
+
+Installation copies the source into the target project; edits here do not
+update installed copies automatically. Consult `specify preset update --help`
+or remove and reinstall manually to update. Check the template stack using
+`specify preset resolve spec-template`, `specify preset resolve plan-template`
+and `specify preset resolve tasks-template`. Overrides or `replace` layers
+may stop lower-priority presets from contributing.

package/content/presets/dart-frog-exceptions/preset.yml

@@ -0,0 +1,25 @@
+schema_version: "1.0"
+
+preset:
+  id: dart-frog-exceptions
+  name: "[DS9] Dart Frog Exceptions"
+  version: "0.1.0"
+  description: "Guidance for shared exceptions and safe failure boundaries."
+
+requires:
+  speckit_version: ">=1.2.1"
+
+provides:
+  templates:
+    - type: template
+      name: spec-template
+      file: templates/spec-template.md
+      strategy: prepend
+    - type: template
+      name: plan-template
+      file: templates/plan-template.md
+      strategy: prepend
+    - type: template
+      name: tasks-template
+      file: templates/tasks-template.md
+      strategy: prepend

package/content/presets/dart-frog-exceptions/templates/plan-template.md

@@ -0,0 +1,25 @@
+## Shared exceptions: planning guidance
+
+For APIs using this preset, shared exception definitions belong in
+`lib/common/exception/`. Reuse existing definitions where compatible; identify
+missing types and do not assume they are already implemented:
+
+- `BusinessException` represents service and repository failures, preserving
+  the domain, appropriate status and original cause and stack for diagnostics.
+- `ClientException` represents failures translated at the controller boundary,
+  with an appropriate status and client-safe message.
+- `MiddlewareException` represents failures at the middleware boundary, with
+  an appropriate status and client-safe message; preserve diagnostic context
+  where applicable.
+
+Plan explicit mappings between boundaries without swallowing failures or
+turning them into success. Preserve approved behavior and response contracts.
+Do not expose original errors, stack traces, credentials, SQL or provider
+details to clients; protect sensitive information in logs as well. Include
+tests for affected failure mappings, status and safe messages.
+
+This preset independently describes exception responsibilities; it does not
+choose an HTTP response format, prescribe retry policies or require another
+preset. If its rules materially conflict with project governance, approved
+contracts or another active preset, record the conflict and seek owner
+direction before dependent decisions.

package/content/presets/dart-frog-exceptions/templates/spec-template.md

@@ -0,0 +1,7 @@
+## Failure behavior guidance
+
+For applicable feature operations, specify observable validation and failure
+behavior, expected status and safe client-facing messages according to the
+approved API contract. Identify missing decisions rather than inventing error
+responses. Preserve existing contracts unless the owner approves a change.
+Internal exception types and their implementation belong in the plan.

package/content/presets/dart-frog-exceptions/templates/tasks-template.md

@@ -0,0 +1,13 @@
+## Shared exceptions: task guidance
+
+Where applicable, generate concrete tasks to reuse or implement
+`BusinessException`, `ClientException` and `MiddlewareException` in
+`lib/common/exception/`, and to map affected failures at the appropriate
+boundaries. Preserve useful original causes and stacks for diagnostics without
+exposing internals or sensitive data to clients or logs.
+
+Include tests for affected error paths, status and safe messages, using the
+approved contract. Do not generate unrelated refactors or change existing
+responses without authorization. Surface material conflicts with project rules
+or other active presets before dependent tasks. Verification tasks are
+required when applicable even if the core template describes tests as optional.

package/content/presets/dart-frog-external-adapters/README.md

@@ -0,0 +1,26 @@
+# External adapters preset
+
+This independent Dart Frog preset guides external HTTP, SDK and other service
+integrations under `lib/common/adapters/<provider>/`. It does not cover
+databases, `common/http` or prescribe retries. Existing integrations are not
+automatically moved or changed. Conflicts with project rules or other presets
+must be presented to the owner.
+
+The three template additions use `prepend` and are visible as Markdown. They
+are planning instructions, not an automated architecture enforcement tool.
+
+## Manual installation
+
+Requires Spec Kit 1.2.1 or later. From the target API repository root, replace
+the example path with the actual location:
+
+```sh
+specify preset add --dev /absolute/path/to/.specify_customs/adapters
+```
+
+Installation copies the source into the target project; edits here do not
+update installed copies automatically. Consult `specify preset update --help`
+or remove and reinstall manually to update. Check the template stack using
+`specify preset resolve spec-template`, `specify preset resolve plan-template`
+and `specify preset resolve tasks-template`. Overrides or `replace` layers
+may stop lower-priority presets from contributing.

package/content/presets/dart-frog-external-adapters/preset.yml

@@ -0,0 +1,25 @@
+schema_version: "1.0"
+
+preset:
+  id: dart-frog-external-adapters
+  name: "[DS9] Dart Frog External Adapters"
+  version: "0.1.0"
+  description: "Guidance for external service integrations in common adapters."
+
+requires:
+  speckit_version: ">=1.2.1"
+
+provides:
+  templates:
+    - type: template
+      name: spec-template
+      file: templates/spec-template.md
+      strategy: prepend
+    - type: template
+      name: plan-template
+      file: templates/plan-template.md
+      strategy: prepend
+    - type: template
+      name: tasks-template
+      file: templates/tasks-template.md
+      strategy: prepend

package/content/presets/dart-frog-external-adapters/templates/plan-template.md

@@ -0,0 +1,28 @@
+## External service adapters: planning guidance
+
+Apply these mandatory rules when the feature needs an external service:
+
+1. Place the technical integration under `lib/common/adapters/<provider>/`.
+   Keep provider-specific DTOs and conversions with the integration when
+   needed. Group integrations by provider; do not create unused files.
+2. Describe the external operation, input and output contracts, configuration,
+   authentication, data boundaries and expected failures. An adapter translates
+   the provider's protocol or SDK and does not own business decisions.
+3. Use project-approved dependency composition and make clients or SDK
+   dependencies replaceable for isolated tests. Reuse an existing configured
+   client or adapter when appropriate; do not assume an SDK is installed.
+4. Define explicit behavior for provider failures and malformed responses,
+   including timeouts where relevant and supported. Do not mask failures with
+   success-shaped defaults. The consumer of the adapter decides whether any
+   retry is appropriate; this preset neither requires nor defines retries.
+5. Keep credentials and sensitive data in approved configuration or secret
+   storage; do not put them in code, logs, artifacts or responses. Capture
+   useful diagnostics without exposing provider internals to consumers.
+6. Plan tests with fake or mocked clients for success, relevant provider
+   failures and malformed responses. Any live integration test requires an
+   explicitly configured non-production environment.
+
+This preset works independently and does not impose a domain architecture,
+database, `common/http` response policy, library or SDK. Preserve existing
+contracts and code unless a change is approved. Record material conflicts with
+other active project rules or presets and seek owner direction.

package/content/presets/dart-frog-external-adapters/templates/spec-template.md

@@ -0,0 +1,11 @@
+## External service integration guidance
+
+When a feature needs an external service, specify the required capability,
+observable outcomes, applicable authorization, data exchanged, side effects,
+and expected behavior on provider failure. Identify unknown contracts or
+security requirements for clarification; do not invent provider behavior.
+
+This guidance applies to external services accessed through HTTP, SDKs or
+other protocols. Databases and the API's `common/http` response handling are
+outside this preset. Apply only relevant guidance; preserve existing behavior
+unless the owner approves a change.

package/content/presets/dart-frog-external-adapters/templates/tasks-template.md

@@ -0,0 +1,17 @@
+## External service adapters: task guidance
+
+For each applicable integration, generate concrete tasks with paths under
+`lib/common/adapters/<provider>/` for the technical adapter, necessary
+provider DTOs and mappings, configuration and dependency composition.
+
+Include tasks for explicit failure handling and isolated tests covering
+successful calls, relevant failures and malformed responses. Protect
+credentials and sensitive data. Add live integration tests only when an
+explicit non-production environment is available and required.
+
+Do not create database or `common/http` tasks because of this preset. Do not
+add a retry policy or change existing integration behavior without an explicit
+requirement. Do not install dependencies without the project's authorization.
+Identify material conflicts with other active rules before dependent tasks.
+These verification tasks are required when applicable, notwithstanding core
+template examples that describe tests as optional.

package/content/presets/dart-frog-hexagonal/README.md

@@ -0,0 +1,44 @@
+# Dart Frog Hexagonal Architecture preset
+
+Version 0.1.0 provides mandatory ports-and-adapters guidance for Dart Frog API
+specifications, plans and tasks. It prepends focused guidance to the standard
+Spec Kit templates instead of replacing their content. It does not choose a
+database, ORM, schema ownership, migration policy or deployment platform.
+
+For external access, a service uses a domain port implemented by a repository;
+the repository is the gateway to the database or to a common external adapter.
+The adapter performs the technical integration with the external service.
+
+The preset describes required planning and task-generation constraints; it is
+not a code linter and does not by itself enforce architectural compliance.
+Existing contracts and project rules remain applicable. Material conflicts
+between the preset, the project constitution, approved contracts or DS9
+guidance must be surfaced to the owner before affected work proceeds.
+
+## Manual installation
+
+Requires Spec Kit 1.2.1 or later. From the target API repository root, with
+access to this source directory, run:
+
+```sh
+specify preset add --dev /absolute/path/to/.specify_customs/hexagonal
+```
+
+Replace the example path with the actual location. This is an explicit,
+per-project installation; creating this directory does not install the preset.
+The CLI copies the source into the target project's `.specify/presets/` and
+registers it there. Later source changes do not update installed copies;
+review the CLI's `specify preset update --help` or remove and reinstall
+manually when an update is desired.
+
+Verify each resolved template in the target project:
+
+```sh
+specify preset resolve spec-template
+specify preset resolve plan-template
+specify preset resolve tasks-template
+```
+
+Project overrides and other presets may take precedence. Check the resolution
+output and the generated template content when troubleshooting. The project
+must still explicitly invoke and approve its own Spec Kit workflows.

package/content/presets/dart-frog-hexagonal/preset.yml

@@ -0,0 +1,25 @@
+schema_version: "1.0"
+
+preset:
+  id: dart-frog-hexagonal
+  name: "[DS9] Dart Frog Hexagonal Architecture"
+  version: "0.1.0"
+  description: "[DS9] Mandatory ports-and-adapters guidance for Dart Frog API artifacts."
+
+requires:
+  speckit_version: ">=1.2.1"
+
+provides:
+  templates:
+    - type: template
+      name: spec-template
+      file: templates/spec-template.md
+      strategy: prepend
+    - type: template
+      name: plan-template
+      file: templates/plan-template.md
+      strategy: prepend
+    - type: template
+      name: tasks-template
+      file: templates/tasks-template.md
+      strategy: prepend

package/content/presets/dart-frog-hexagonal/templates/plan-template.md

@@ -0,0 +1,57 @@
+<!--
+[DS9] Dart Frog Hexagonal Architecture preset: mandatory planning guidance
+
+These rules apply to Dart Frog APIs where this preset is installed. Read the
+project constitution, project context, applicable approved specifications and
+contracts, and relevant DS9 guidance. Distinguish existing implementations from
+planned work. If a local rule, approved source contract or DS9 recommendation
+materially conflicts with a rule below, record the exact conflict and request
+owner direction before planning the affected work. Do not silently relax the
+preset or change existing behavior.
+
+Include a feature-specific architecture check in the completed plan:
+
+1. Identify affected business contexts and use the applicable parts of
+   lib/<context>/domain/{models,ports,services} and
+   lib/<context>/adapter/{controllers,dtos,repository}. Identify routes/ and
+   test/ paths. Reuse existing components; do not invent unused layers or
+   create every directory when the feature does not need it.
+2. Show the dependency direction: route -> controller -> service -> port <-
+   repository -> database or common external adapter -> external service.
+   The repository implements the port and is the gateway to the external
+   world, including databases and integrations. Services must not call
+   common external adapters, SDKs, database clients or other infrastructure
+   directly. Domain models, ports and services must not depend on Dart Frog,
+   HTTP request/response types, DTOs, database/ORM types, infrastructure
+   implementations or external SDKs. Ports expose typed domain contracts;
+   services depend on ports, not concrete repositories.
+3. Assign business rules and orchestration to services; HTTP adaptation and
+   input validation to controllers/DTOs; gateway orchestration and mapping to
+   repositories; technical external calls to the common adapter or database
+   client used by the repository; and only method dispatch and response
+   conversion to routes. Unsupported HTTP methods return 405.
+4. Plan constructor injection for service and repository dependencies and
+   runtime composition through scoped Dart Frog middleware/providers.
+   Handlers must not construct services or repositories. Shared infrastructure
+   may be provided by the project's approved composition root; it does not
+   replace injection. Follow local controller and import conventions.
+5. Plan typed failure contracts for fallible controller, service, repository
+   and port operations using fpdart TaskEither: BusinessException for services
+   and repositories, ClientException for controllers, and MiddlewareException
+   at middleware boundaries. Map failures explicitly and keep 5xx responses
+   free of internal details. Pure operations without I/O may return plain
+   values. Reuse existing error types and contracts; do not assume they exist.
+6. Describe endpoint contracts, validation, authentication/authorization,
+   error mapping and affected data/integration boundaries. Preserve approved
+   behavior and contracts; record unresolved conflicts instead of silently
+   introducing exceptions. No database, ORM, schema ownership or migration
+   policy is imposed by this preset.
+7. Plan proportionate verification: service business rules with mocked or fake
+   ports, relevant controller and route contracts including 405, failure and
+   authorization paths, and isolated external boundaries. Include project
+   analysis and test commands when applicable; integration tests must use an
+   explicitly configured non-production environment.
+
+Do not install or upgrade dependencies without the project's required
+authorization. Document missing prerequisites and required owner decisions.
+-->

package/content/presets/dart-frog-hexagonal/templates/spec-template.md

@@ -0,0 +1,23 @@
+<!--
+[DS9] Dart Frog Hexagonal Architecture preset: specification guidance
+
+This preset establishes mandatory architectural constraints for Dart Frog APIs
+where it is installed. Consult the project's constitution, context, approved
+contracts and applicable DS9 guidance. If they materially conflict with this
+preset, identify the conflict and seek owner direction before making a dependent
+decision; do not silently override either rule or assume an exception.
+
+Keep the specification focused on observable behavior rather than prescribing
+classes, files or infrastructure. For each affected API operation, specify the
+method and path, actors and authorization, inputs and validation, successful
+responses, failure behavior, and independently verifiable acceptance criteria.
+Record business rules, relevant data boundaries, side effects and existing
+contracts that must be preserved. Mark unknown material behavior for
+clarification rather than inventing it.
+
+The implementation must respect ports and adapters: business rules must be
+independent of HTTP, frameworks, databases and external SDKs. Architectural
+details and affected components belong in the plan and tasks. This preset does
+not select a database, ORM, migration policy or deployment environment, and it
+does not authorize changes to established behavior or public contracts.
+-->

package/content/presets/dart-frog-hexagonal/templates/tasks-template.md

@@ -0,0 +1,34 @@
+<!--
+[DS9] Dart Frog Hexagonal Architecture preset: mandatory task-generation guidance
+
+Consult the approved spec, plan, constitution and relevant project context.
+If the plan or another applicable rule materially conflicts with this preset,
+identify the conflict and request owner direction before generating tasks that
+depend on an unresolved decision. Preserve existing behavior and contracts;
+do not infer authorization for a migration, dependency change or refactor.
+
+Generate concrete, story-scoped tasks with actual paths and dependencies for
+the applicable work, not a fixed checklist of files:
+- Domain models and typed ports; business rules and orchestration in services.
+- Controllers/DTOs for HTTP adaptation; repositories that implement ports and
+  act as gateways to databases and common external adapters, mapping external
+  data; thin routes and 405 handling. Services do not call common adapters,
+  SDKs or database clients directly.
+- Constructor injection and middleware/provider composition. Reuse the
+  project's approved shared infrastructure instead of duplicating it.
+- Fallible layer contracts using TaskEither and the appropriate
+  BusinessException, ClientException or MiddlewareException boundary, with
+  explicit safe error mapping and preservation of approved HTTP contracts.
+- Tests for changed business rules using mocked or fake ports, plus applicable
+  validation, controller, route, 405, authorization and failure-path tests.
+  Isolate external systems in unit tests and use a configured non-production
+  environment for integration tests.
+- Relevant analysis and test commands and documentation updates. Identify
+  missing prerequisites without adding dependencies or migrations implicitly.
+
+These verification tasks are required whenever applicable even if the core
+template's sample language describes tests as optional. Keep the existing
+checklist format, user-story grouping and independent acceptance criteria.
+Never generate unused layers or database/ORM-specific tasks solely because
+this preset is installed.
+-->

package/dist/src/index.js

@@ -3,7 +3,8 @@
  * Ponto de entrada do pacote (o `bin` do npm aponta para este arquivo).
  * Um único executável, dois modos:
  *   - `ds9-mcp`        -> sobe o servidor MCP via stdio (é o que a IDE executa);
- *   - `ds9-mcp init`   -> configura a IDE do usuário e sai.
+ *   - `ds9-mcp init`   -> configura a IDE do usuário e sai;
+ *   - `ds9-mcp presets`-> lista/instala presets Spec Kit (via `specify preset add`).
  * Manter os dois no mesmo comando permite que o `npx -y @ds9-solutions/mcp` sirva a ambos.
  */
 import { createInterface } from "node:readline/promises";
@@ -12,6 +13,7 @@ import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js"
 import { loadEntries } from "./content.js";
 import { createServer } from "./server.js";
 import { TARGETS, runInit } from "./init.js";
+import { hasSpecify, installHint, installPreset, loadPresets } from "./presets.js";
 // A versão vem do package.json para existir uma única fonte (o que foi publicado no npm).
 const pkg = JSON.parse(readFileSync(new URL("../../package.json", import.meta.url), "utf8"));
 /** Lê `--nome valor` dos argumentos. Parser mínimo de propósito: evita uma dependência de CLI. */
@@ -44,16 +46,45 @@ async function init(args) {
         console.log(`✔ Instruções adicionadas em ${result.agentsFile}`);
     console.log("Reinicie a IDE/agente para carregar o servidor.");
 }
+/** Modo `presets`: `presets list` ou `presets add <id> [--priority N] [--dir pasta]`. */
+function presets(args) {
+    const [action, id] = args;
+    const all = loadPresets();
+    if (action === "list" || !action) {
+        for (const p of all)
+            console.log(`- ${p.id} v${p.version}: ${p.description}\n  ${installHint(p.id)}`);
+        if (!hasSpecify())
+            console.log("\n⚠ Spec Kit (`specify`) não encontrado no PATH.");
+        return;
+    }
+    if (action !== "add" || !id) {
+        console.error("Uso: ds9-mcp presets list | presets add <id> [--priority N] [--dir pasta]");
+        process.exit(1);
+    }
+    const priority = flag(args, "priority");
+    const out = installPreset(all, id, flag(args, "dir") ?? process.cwd(), {
+        priority: priority !== undefined ? Number(priority) : undefined,
+    });
+    process.stdout.write(out);
+    console.log(`✔ Preset ${id} instalado`);
+}
 /** Modo servidor: carrega o conteúdo e fica atendendo a IDE pela entrada/saída padrão. */
 async function serve() {
-    const server = createServer(loadEntries(), pkg.version);
+    const server = createServer(loadEntries(), pkg.version, loadPresets());
     await server.connect(new StdioServerTransport());
     // stderr: o stdout pertence ao protocolo MCP e não pode receber logs.
     console.error(`[ds9-mcp] v${pkg.version} pronto (stdio)`);
 }
 // Qualquer erro vira mensagem curta + código de saída 1, em vez de um stack trace assustador.
 const [command, ...rest] = process.argv.slice(2);
-(command === "init" ? init(rest) : serve()).catch((err) => {
+const run = async () => {
+    if (command === "init")
+        return init(rest);
+    if (command === "presets")
+        return presets(rest);
+    return serve();
+};
+run().catch((err) => {
     console.error(err instanceof Error ? err.message : err);
     process.exit(1);
 });

package/dist/src/presets.js

@@ -0,0 +1,65 @@
+/**
+ * Presets do Spec Kit distribuídos pela DS9 (`presets/<id>/preset.yml` + `templates/`).
+ *
+ * A instalação é delegada ao `specify preset add --dev <pasta>`: é o Spec Kit quem copia os
+ * arquivos e mantém o `.specify/presets/.registry` (hash, prioridade). Nunca escrevemos nele.
+ */
+import { execFileSync, spawnSync } from "node:child_process";
+import { existsSync, readdirSync, readFileSync } from "node:fs";
+import { join } from "node:path";
+import { parse as parseYaml } from "yaml";
+import { resolveContentRoot } from "./content.js";
+export const PRESET_ID = /^[a-z0-9][a-z0-9-]{0,63}$/;
+/** Lê os presets do conteúdo. Pasta ausente ou manifesto inválido são ignorados, sem quebrar o servidor. */
+export function loadPresets(root = resolveContentRoot()) {
+    const base = join(root, "presets");
+    if (!existsSync(base))
+        return [];
+    const presets = [];
+    for (const dirent of readdirSync(base, { withFileTypes: true })) {
+        const manifest = join(base, dirent.name, "preset.yml");
+        if (!dirent.isDirectory() || !PRESET_ID.test(dirent.name) || !existsSync(manifest))
+            continue;
+        try {
+            const meta = parseYaml(readFileSync(manifest, "utf8"))
+                ?.preset;
+            presets.push({
+                id: dirent.name,
+                name: String(meta?.name ?? dirent.name),
+                version: String(meta?.version ?? "0.0.0"),
+                description: String(meta?.description ?? ""),
+                dir: join(base, dirent.name),
+            });
+        }
+        catch {
+            // manifesto ilegível: o preset simplesmente não é listado
+        }
+    }
+    return presets.sort((a, b) => a.id.localeCompare(b.id));
+}
+/** Comando que o usuário/agente pode rodar manualmente (o caminho real do pacote varia por máquina). */
+export const installHint = (id) => `npx -y @ds9-solutions/mcp presets add ${id}`;
+/** true quando o executável `specify` (Spec Kit) está no PATH. */
+export function hasSpecify() {
+    return spawnSync("specify", ["--version"], { stdio: "ignore" }).status === 0;
+}
+/**
+ * Instala um preset no projeto com `specify preset add --dev`. Sem shell (execFile), e o id só é
+ * aceito se existir na lista carregada, então nada vindo do usuário vira caminho ou comando.
+ */
+export function installPreset(presets, id, projectDir, opts = {}) {
+    const preset = presets.find((p) => p.id === id);
+    if (!preset) {
+        throw new Error(`Preset "${id}" não encontrado. Disponíveis: ${presets.map((p) => p.id).join(", ") || "(nenhum)"}`);
+    }
+    if (!hasSpecify()) {
+        throw new Error("Spec Kit (`specify`) não encontrado no PATH. Instale-o (https://github.com/github/spec-kit) e rode de novo.");
+    }
+    if (!existsSync(join(projectDir, ".specify"))) {
+        throw new Error(`${projectDir} não é um projeto Spec Kit (sem .specify/). Rode \`specify init --here\` antes.`);
+    }
+    const args = ["preset", "add", "--dev", preset.dir];
+    if (opts.priority !== undefined)
+        args.push("--priority", String(opts.priority));
+    return execFileSync("specify", args, { cwd: projectDir, encoding: "utf8" });
+}

package/dist/src/server.js

@@ -10,6 +10,7 @@ import { McpServer, ResourceTemplate } from "@modelcontextprotocol/sdk/server/mc
 import { z } from "zod";
 import { rankByMetadata, searchBodies } from "./search.js";
 import { isSafeRelativePath, MAX_PATH_LENGTH, SKILL_ID } from "./skill-files.js";
+import { installHint } from "./presets.js";
 // Enviado ao host no handshake. Hosts sem suporte nativo a skills/agentes dependem disto (e do
 // bloco no AGENTS.md) para saber que devem consultar o servidor antes de implementar.
 const INSTRUCTIONS = [
@@ -28,7 +29,7 @@ const text = (t, isError = false) => ({
  * Cria o servidor sobre uma lista de entradas já carregada. Receber as entradas por parâmetro
  * (em vez de ler do disco aqui) permite testar o servidor com conteúdo controlado.
  */
-export function createServer(entries, version = "0.0.0") {
+export function createServer(entries, version = "0.0.0", presets = []) {
     const server = new McpServer({ name: "ds9", version }, { instructions: INSTRUCTIONS });
     // Helpers de consulta sobre as entradas.
     const byKind = (kind) => entries.filter((e) => e.kind === kind);
@@ -177,5 +178,14 @@ export function createServer(entries, version = "0.0.0") {
         }
         return text(`Skills recomendadas (use get_skill):\n${listing(skills)}\n\nAgentes recomendados (use get_agent):\n${listing(agents)}`);
     });
+    // list_presets — somente leitura: o MCP não instala nada; devolve o comando para o usuário rodar.
+    server.registerTool("list_presets", {
+        description: "Lista os presets Spec Kit da DS9 disponíveis e o comando para instalá-los no projeto (via `specify preset add`).",
+        annotations: { readOnlyHint: true },
+    }, async () => text(presets.length
+        ? presets
+            .map((p) => `- ${p.id} v${p.version}: ${p.description}\n  instalar: ${installHint(p.id)}`)
+            .join("\n")
+        : "(nenhum preset disponível)"));
     return server;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ds9-solutions/mcp",
-  "version": "0.4.0",
+  "version": "0.6.0",
   "description": "Servidor MCP da DS9: expõe skills e subagentes oficiais para qualquer IDE/LLM com suporte a MCP",
   "type": "module",
   "license": "UNLICENSED",