crewkit 1.1.4 → 1.1.6

package/skill/adapters/cursor.md

@@ -1,215 +0,0 @@
-# Adapter: Cursor
-
-This adapter is executed during Phase 7, Step 10 of `/crewkit-setup`.
-You are the AI. Follow every instruction in this file to generate Cursor-compatible context files.
-
-**Input:** Read `.crewkit/last-scan.md` for the project profile. The Claude Code files generated in Steps 1-9 are your source of truth.
-**Output:** Files under `.cursor/rules/` and `AGENTS.md` at the project root.
-
----
-
-## Rules for this adapter
-
-1. All generated files MUST be in **English**.
-2. Do NOT duplicate `.ai/memory/` — it is shared between all IDEs. No transformation needed.
-3. `model:` frontmatter from `.claude/agents/*.md` is Claude Code-only — strip it.
-4. Cursor has no equivalent for skills/prompts — skip `.claude/skills/` entirely.
-5. Create `.cursor/rules/` directory if it does not exist.
-
----
-
-## Step U1 — `.cursor/rules/project.md`
-
-**Source:** `CLAUDE.md`
-**Transformation:** Reformat for Cursor. Add required frontmatter. Remove agent/skill/hook sections that are Claude Code-specific.
-
-**Required Cursor frontmatter:**
-```markdown
----
-description: "Project rules"
-alwaysApply: true
----
-```
-
-**Expected output format:**
-```markdown
----
-description: "Project rules"
-alwaysApply: true
----
-# [PROJECT NAME] — Project Rules
-
-## Overview
-[1-2 sentences from CLAUDE.md overview — what the project is, main stack]
-[Business domain: what it does, core entities, risk profile]
-
-**Stack:** [stacks]
-**Architecture:** [key patterns]
-
----
-
-## Hard rules (apply to every response)
-
-[Numbered list — copy from CLAUDE.md hard rules verbatim.]
-
-1. [Rule 1]
-2. [Rule 2]
-...
-
-Details for each rule → `.ai/memory/conventions.md`
-
----
-
-## Project Memory (`.ai/memory/`)
-
-Load context on demand:
-
-| File | When to load |
-|------|-------------|
-| `architecture.md` | Always — modules, layers, dependencies |
-| `conventions.md` | Always — naming, patterns, anti-patterns |
-| `commands.md` | When running build/test/deploy |
-| `testing.md` | When creating or running tests |
-| `lessons-{domain}.md` | When working on that domain |
-
----
-
-## Output Format
-
-Always return:
-- **Summary** — what was done
-- **Files changed** — list with brief description
-- **Tests** — pass/fail count (if tests were run)
-- **Risks / Next steps** — if any
-```
-
-**What to REMOVE from CLAUDE.md:**
-- `## Agent Discipline` section
-- `## Skills (slash commands)` section
-- `## Architect Decision Gate` section
-- `## Test Safety Loop` section
-
----
-
-## Step U2 — `.cursor/rules/*.md`
-
-**Source:** `.claude/rules/*.md`
-**Transformation:** Convert frontmatter to Cursor format. Keep glob patterns and all rule content unchanged.
-
-Claude Code frontmatter format:
-```markdown
----
-description: "Node.js coding rules — applied when editing src/**/*.{js,ts}"
-globs: "src/**/*.{js,ts}"
----
-```
-
-Cursor frontmatter format:
-```markdown
----
-description: "Node.js coding rules"
-globs: "src/**/*.{js,ts}"
----
-```
-
-**Mapping:**
-- `globs:` → `globs:` (keep as-is — Cursor uses the same key)
-- `description:` → keep as-is, but shorten to the rule name without the "applied when editing..." suffix if present
-- Body: copy verbatim
-
-**File naming:** `.claude/rules/dotnet.md` → `.cursor/rules/dotnet.md`
-Keep the same filename — just place it under `.cursor/rules/`.
-
-**Example — source `.claude/rules/python.md`:**
-```markdown
----
-description: "Python coding rules — applied when editing **/*.py"
-globs: "**/*.py"
----
-
-# Python Rules
-
-- Use type hints on all function signatures
-- Validate input with Pydantic models at API boundaries
-```
-
-**Example — target `.cursor/rules/python.md`:**
-```markdown
----
-description: "Python coding rules"
-globs: "**/*.py"
----
-
-# Python Rules
-
-- Use type hints on all function signatures
-- Validate input with Pydantic models at API boundaries
-```
-
----
-
-## Step U3 — `AGENTS.md` (project root)
-
-**Source:** All `.claude/agents/*.md` files
-**Transformation:** Concatenate all agents into a single markdown file with `##` sections. Strip `model:` frontmatter from each. Remove the `<!-- crewkit:context-start -->...<!-- crewkit:context-end -->` block from each agent. Keep the `name:` and `description:` from frontmatter and all agent instructions.
-
-**Output format:**
-```markdown
-# Agents
-
-This file describes the AI agents available in this project.
-Each agent has a specific role and scope. Invoke the appropriate agent for each task type.
-
----
-
-## [Agent Name]
-
-> [description from frontmatter]
-
-[agent body — full instructions, stripped of model: and crewkit context block]
-
----
-
-## [Agent Name 2]
-
-> [description from frontmatter]
-
-[agent body]
-
----
-```
-
-**Agent order:** explorer, architect, coder, tester, reviewer (same order as in `.claude/agents/`).
-
-**What to strip from each agent:**
-- `model:` frontmatter line
-- `name:` frontmatter line (becomes the `## heading` instead)
-- `description:` frontmatter line (becomes the `> blockquote` instead)
-- The entire `<!-- crewkit:context-start -->...<!-- crewkit:context-end -->` block (inclusive)
-- The YAML frontmatter delimiters (`---`) — the content moves to the `##` section body
-
-**File location:** `AGENTS.md` at the project root (not under `.cursor/`).
-
----
-
-## Step U4 — Skills
-
-**Source:** `.claude/skills/`
-**Action:** Skip entirely. Cursor has no equivalent concept for skills or prompts.
-
-Do NOT generate any file for this step. Log: "Cursor adapter: skills skipped (no Cursor equivalent)."
-
----
-
-## Completion Checklist — Cursor Adapter
-
-Before reporting done, verify each item:
-
-- [ ] `.cursor/rules/project.md` — exists, has `alwaysApply: true` frontmatter, contains hard rules, does NOT contain Agent Discipline or slash command sections
-- [ ] `.cursor/rules/` — one `.md` file per `.claude/rules/*.md` source file (plus `project.md`)
-- [ ] `.cursor/rules/*.md` — each has `globs:` frontmatter matching the source rule file
-- [ ] `AGENTS.md` — exists at project root, has `##` section for each of the 5 agents
-- [ ] `AGENTS.md` — no `model:` lines, no `crewkit:context-start` blocks, no YAML frontmatter delimiters
-- [ ] `.ai/memory/` — NOT duplicated under `.cursor/` (shared, no copy needed)
-- [ ] `.claude/skills/` — NOT copied (no Cursor equivalent, intentionally skipped)
-- [ ] No Portuguese in any generated file

package/skill/cursor-global.md

@@ -1,157 +0,0 @@
----
-description: "Context engineering setup — scan codebase and generate AI context files (.cursor/rules, AGENTS.md, .ai/memory)"
-alwaysApply: false
----
-
-# crewkit-setup
-
-Scan the current project and generate a complete context engineering setup tailored to this codebase.
-
-**You are the AI executing this.** Follow each phase in order. Do not ask the user questions. Scan, generate, report.
-
----
-
-## Phase 1 — Reconnaissance
-
-Scan the project to identify:
-- **Stack & frameworks**: languages, build tools, test frameworks, package managers
-- **Architecture**: monolith/microservices, key directories, entry points
-- **Existing AI context**: any `.cursor/`, `.github/`, `.ai/`, `CLAUDE.md`, `AGENTS.md` files
-
-Write findings to `.crewkit/scan-phase1-recon.md`.
-
----
-
-## Phase 2 — Codebase Mapping
-
-Read representative source files (3-5 per layer: models, services, controllers, tests). Identify:
-- Naming conventions, code style
-- Core domain concepts and entities
-- Test patterns and coverage approach
-- CI/CD and build commands
-
-Write findings to `.crewkit/scan-phase2-map.md`.
-
----
-
-## Phase 3 — Profile Compilation
-
-Synthesize phases 1-2 into a project profile:
-- Stack summary
-- Architecture summary
-- Key commands (build, test, lint)
-- Domain concepts
-- Hard rules to enforce
-
-Write profile to `.crewkit/last-scan.md`.
-
----
-
-## Phase 4 — File Generation
-
-Generate all files using the profile from `.crewkit/last-scan.md`.
-
-### Step 1 — `.ai/memory/`
-
-Create these files (all in English):
-- `architecture.md` — system design, key components, data flow
-- `conventions.md` — naming rules, patterns, anti-patterns
-- `commands.md` — build, test, lint, run commands with flags
-- `testing.md` — test strategy, frameworks, coverage approach
-- `lessons.md` — known gotchas, non-obvious behaviors
-- `state.md` — current sprint goal, recent changes, open issues
-
-### Step 2 — `.cursor/rules/project.md`
-
-```
----
-description: "Project rules"
-alwaysApply: true
----
-# [PROJECT NAME] — Project Rules
-
-## Overview
-[1-2 sentences: what the project is, main stack]
-
-**Stack:** [stacks]
-**Architecture:** [key patterns]
-
----
-
-## Hard rules
-
-[Numbered list of non-negotiable rules from the profile]
-
----
-
-## Memory
-
-Reference files in `.ai/memory/` for detailed context:
-- `.ai/memory/architecture.md` — system design
-- `.ai/memory/conventions.md` — coding conventions
-- `.ai/memory/commands.md` — build/test commands
-```
-
-### Step 3 — `.cursor/rules/` (per-stack rules)
-
-For each detected stack (e.g., `typescript.md`, `python.md`), generate a rules file with:
-```
----
-description: "[Stack] coding rules"
-globs: ["**/*.ts"] (or appropriate glob)
-alwaysApply: false
----
-[Stack-specific rules: error handling, imports, typing, testing patterns]
-```
-
-### Step 4 — `AGENTS.md`
-
-Create a single `AGENTS.md` at the project root with all agents as `##` sections:
-
-```markdown
-# Agents
-
-## Explorer
-Role: Codebase reconnaissance and research.
-[...]
-
-## Architect
-Role: System design and planning.
-[...]
-
-## Coder
-Role: Implementation.
-[...]
-
-## Tester
-Role: Test writing and validation.
-[...]
-
-## Reviewer
-Role: Code review and quality.
-[...]
-```
-
-Each agent section should include: Role, Responsibilities, Approach, Output format.
-
----
-
-## Phase 5 — Completion Report
-
-After all files are generated, report to the user:
-
-```
-crewkit-setup complete
-
-Generated:
-  .ai/memory/          (6 files)
-  .cursor/rules/       (project.md + per-stack rules)
-  AGENTS.md            (5 agents)
-
-Stack detected: [stack]
-Architecture:   [pattern]
-
-Next steps:
-  1. Review .cursor/rules/project.md — adjust hard rules if needed
-  2. Open Cursor and start coding — context is active
-```