@ancleto/spec 0.2.0 → 0.2.1

package/templates/PRODUCT.md

@@ -1,57 +1,43 @@
 # Product Context - [Product Name]
 
-> **This file is EXTENSIBLE and will never be replaced by @ancleto/ai-tooling-framework**
+> **This file is EXTENSIBLE and will never be replaced by @ancleto/spec**
 >
-> Fill in the sections according to your product/project. This file is read by AI agents (Claude, Cursor, etc.) to understand the specific context of your product.
-
-> **How to complete this file:** replace `[Product Name]` in the title and fill each section with your product's real values, deleting the example/placeholder text as you go. At a minimum, complete **Project Type**, **Tech Stack**, **Azure DevOps**, **AI Memory**, **Project Structure**, and **Project Commands** — agents rely on these to operate in your repo. The remaining sections are optional but recommended.
+> Fill in the sections according to your product/project. AI agents read this file to understand product-specific context.
 
 ## Project Type
 
-_Describe the project type: Web App, API, Library, Monorepo, etc._
-
-**Example:**
-
-- Web application with SSR
-- REST API with Node.js
-- Shared TypeScript library
-- Nx/Lerna monorepo
+- _Describe: Web App, REST API, Library, Monorepo, etc._
 
 ---
 
 ## Tech Stack
 
-_List the project's main technologies._
+- **Runtime**: Node.js >=24.x
+- **Language**: TypeScript
+- **Framework**: _(e.g., Next.js / Express / React / NestJS)_
+- **Testing**: _(e.g., Node Test Runner / Vitest / Jest)_
+- **Infra / CI/CD**: _(e.g., GitHub Actions / AWS / Docker)_
 
-**Base stack:**
+---
 
-- **Runtime**: Node.js 20.x
-- **Language**: TypeScript
-- **Build**: Nx / Webpack / Vite (depending on the project)
-- **Testing**: Jest + Testing Library
-- **CI/CD**: Azure DevOps
+## AI Memory (.ancleto/memory.db)
 
-**Additional per project:**
+- **Repository App ID**: ancleto.[Product Name]
+- **Scope**: `project:[Product Name]`
 
-- Framework: React / Vue / Angular / Express
-- State: Redux / Context / Zustand
-- Styling: TailwindCSS / Sass / CSS-in-JS
-- Infra: AWS CDK / Serverless / Containers
+> Memory for this repository is persisted locally in `.ancleto/memory.db` (SQLite + FTS5).
+> Agents store architectural decisions and rules here automatically. It never leaves the repo.
 
 ---
 
-## Azure DevOps
+## Azure DevOps (Optional)
 
-_How this project retrieves work items and other Azure DevOps resources. AI agents read this to resolve cards._
-
-**Fill in for your project:**
+_Fill in ONLY if this project uses Azure DevOps for Work Items._
 
 - **Organization URL**: https://dev.azure.com/your-org
 - **Team Project**: YourProject
 
-Keep the `Organization URL` value as a plain URL, on a line containing the words `Organization URL` — the fetch command below reads it from here with a `grep`.
-
-**Work items (card fetch):** via the `az` CLI (`azure-devops` extension), in a single call:
+**Work item fetch command (single-line CLI execution):**
 
 ```bash
 ORG=$(grep -Eim1 '\*\*(Organization URL|Organization)\*\*:' PRODUCT.md | grep -oE 'https?://[^ `"]+') && \
@@ -60,46 +46,22 @@ az boards work-item show --id <id> --org "$ORG" --expand none --fields System.Id
  | fold -s -w 200
 ```
 
-- **Required inputs**: `id` (card number) + `org`. Do NOT pass `--project` — it fails with `unrecognized arguments: --project`; the id is org-global and the project comes back as `System.TeamProject`.
-- **The organization is read from this file by the shell**, from the `Organization URL` line above — one substitution inside the same call, instead of an agent reading this whole file into its context.
-- **Always project with `--expand none --fields`**: the CLI defaults to `--expand all` and returns the entire work item. `--fields` without `--expand none` fails with `The expand parameter can not be used with the fields parameter`.
-- **`sed` + `fold` are not cosmetic**: `System.Description` arrives as a single HTML line that can exceed 70.000 characters, and the agent runtime truncates long lines at 2.000 — without them the agent silently receives a fraction of the description.
-- **Response fields used** (`.fields`): `System.Id`, `System.Title`, `System.Description`, `Microsoft.VSTS.Common.AcceptanceCriteria`, `System.WorkItemType`, `System.TeamProject`, `System.State`.
-- **Setup/auth**: requires `az extension add --name azure-devops`; `az login` (AAD) is enough — a PAT (`AZURE_DEVOPS_EXT_PAT`) only as a fallback.
-
-## AI Memory
-
-- **Repository App ID**: ancleto.YourProject
-
-`Repository App ID` identifies this repository in the shared mem0 store. Agents use it to isolate memories from other repositories. It must be unique to this repository, not shared across the Azure DevOps team project.
-
-`Team Project` from the Azure DevOps section is stored as `project_id` in mem0. Complete both `Repository App ID` and `Team Project` before using AI memory.
+- **Required inputs**: `id` + `org` (leído del campo `Organization URL` por `grep`). No pasar
+  `--project` (falla).
+- `--expand none --fields` es obligatorio (el default `--expand all` trae el work item completo).
+- `sed` + `fold` no son cosméticos: `System.Description` llega en una sola línea HTML de hasta
+  70k chars y el runtime trunca a 2k sin ellos.
+- Setup: `az extension add --name azure-devops`; alcanza con `az login`.
 
 ---
 
 ## Project Structure
 
-_Describe the project's main folder structure._
-
-**Example for a monorepo:**
-
-```
-libs/                    # Shared libraries
-apps/                    # Applications
-tools/                   # Build tools
-openspec/               # OpenSpec configuration
-  config.yaml           # Project context
-  changes/              # Active changes
-```
-
-**Example for a standalone app:**
-
-```
+```text
 src/
-  components/           # Reusable components
-  features/             # Business features
-  services/             # Services and APIs
-  utils/                # Utilities
+  components/
+  features/
+  services/
 openspec/
   config.yaml
   changes/
@@ -109,72 +71,21 @@ openspec/
 
 ## Critical Files & Guardrails
 
-_Project-specific critical files or folders that require special care._
-
 **Take special care when modifying:**
 
-**Example:**
-
-- Code in `src/core/` (affects the whole app)
-- Routing configuration
-- Shared assets
-- Infrastructure (CDK, Terraform, etc.)
+- Core business logic in `src/core/`
+- Infrastructure definitions & Environment variables
 
 **Avoid:**
 
-- Architecture changes without documenting them in OpenSpec
-- Introducing new dependencies without reviewing existing ones
-- Modifying established conventions without team consensus
+- Uncommunicated breaking changes in public APIs
+- Adding external dependencies without checking existing ones
 
 ---
 
 ## Project Commands
 
-_The project's most important npm/yarn/pnpm commands._
-
-**Example:**
-
 - `npm run dev` → Development server
 - `npm test` → Run tests
 - `npm run build` → Production build
 - `npm run lint` → Linter
-- `npm run deploy` → Deploy (per environment)
-
----
-
-## Team Guidelines
-
-_Team-specific conventions, patterns, and guides._
-
-**You can add:**
-
-- Specific naming conventions
-- Preferred design patterns
-- Architecture guides
-- Links to internal documentation
-- Reference contacts
-
----
-
-## Custom Commit Rules
-
-_Project-specific commit rules (in addition to the Conventional Commits convention defined in `CONTRIBUTING.md` and `AGENTS.md`)._
-
-**Example:**
-
-- Use a specific scope for modules: `feat(auth):`, `fix(payments):`
-- Include the ticket number in the commit: `feat(auth): add OAuth #JIRA-123`
-- Team-specific breaking-change format
-
----
-
-## Custom Agent Configuration
-
-_Agent configuration specific to this project._
-
-**Example:**
-
-- Code style preferences
-- Patterns to follow/avoid
-- Custom workflows
-- Specific testing rules

package/templates/CONTRIBUTING.md

@@ -1,25 +0,0 @@
-# Contributing
-
-Guía de contribución para este repositorio personal.
-
-## Flujo
-
-1. Crear rama de features: `feat/`, `fix/`, `chore/`
-2. Commits en formato Conventional Commits:
-   - `feat(scope): descripcion en presente`
-   - `fix(scope): descripcion en presente`
-   - `chore(scope): descripcion en presente`
-   - `docs(scope): ...`
-   - `refactor(scope): ...`
-   - `test(scope): ...`
-4. Abrir PR/merge request contra `main` con título semántico y plan de pruebas cuando aplique.
-5. No forzar push ni saltar hooks de validación.
-
-## Validaciones
-
-Correr antes de cerrar un cambio (según el proyecto):
-
-- `npm run typecheck` / `tsc --noEmit`
-- `npm run lint`
-- `npm test`
-- `npm run build`