Repository navigation
v1.5 — repositioning (dev-tool-first) + namespace migration - #10
Merged
Merged
Conversation
Clarifies what acture is and renames the package suite to match. Positioning: - docs/positioning.md (canonical): acture is a development tool first — delivered primarily as skills/patterns/codemods; the packages are an optional accelerator. A developer must be able to use acture with zero acture-* dependency unless they explicitly choose otherwise. Two flexibility dimensions: core vs strangler-fig; agent-written vs package-reuse. - New skill acture-consumer-integration: the foundational pattern for building a consumer (palette, hotkeys, MCP, AI, e2e, macros, …) in a target project. Dev skills (architecture-primer, hard-donts, palette-design) now load it whenever a task touches a consumer; the hard-donts merge ritual gained a positioning check. - AGENTS.md + root README + all 15 package READMEs carry the dev-tool-first framing. Namespace migration: - All 13 @acture/* packages renamed to unscoped acture-* (the @Acture npm scope was unavailable; flat naming also fits the optional-tools positioning). Imports, workspace deps, configs, changeset config, examples, docs, and skills updated; lockfile regenerated. - acture and eslint-plugin-acture-migration keep their (already-published) names. The 13 renamed packages are built/tested and ready to publish. Plan restructure: - docs/roadmap.md: forward plan + full done/not-done tracking. - docs/next_session.md: next step is an acture-core positioning-alignment review. The v1.4-era handoff is parked in docs/backlog/. 396 package tests + 41 example tests green; all 15 packages build + typecheck.
thorwhalen
added a commit
that referenced
this pull request
May 15, 2026
Per-surface consumer skills for the three surfaces that already have shipping packages (acture-hotkeys, acture-mcp-server, acture-ai-vercel). All three build on acture-consumer-integration and follow the v1.7 macros/e2e template — document both the agent-written path and the package-reuse path with the tool-library choice framed as the user's. - acture-hotkeys: keyboard shortcuts as a registry projection - acture-mcp: the registry as an MCP server (two-layer split, security guardrails per hard-don'ts #5/#10) - acture-ai: the registry as LLM tool definitions (the schema-projection fork: Zod passthrough vs JSON Schema) - acture-architecture-primer + acture-consumer-integration wired to the new skills (consumer-surface list + See also) Skills + docs only — no package code changed, no changeset. Full write-up in docs/v1_8-reflection.md.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Clarifies what acture is and renames the package suite to match.
Positioning
docs/positioning.md(new, canonical) — acture is a development tool first: delivered primarily as skills/patterns/codemods, with theacture-*packages as an optional accelerator. A developer must be able to use acture with zeroacture-*dependency unless they explicitly opt in. Two flexibility dimensions: core vs strangler-fig; agent-written vs package-reuse.acture-consumer-integrationskill — the foundational pattern for building a consumer (palette, hotkeys, MCP, AI, e2e, macros) in a target project. Dev skills (acture-architecture-primer,acture-hard-donts,acture-palette-design) now load it whenever a task touches a consumer;acture-hard-dontsgained a positioning check (merge-ritual item ci(release): drop the head_commit.message guard that broke workflow parsing #6).AGENTS.md, root README, and all 15 package READMEs carry the dev-tool-first framing.Namespace migration
@acture/*packages renamed to unscopedacture-*— the@acturenpm scope was unavailable, and flat naming fits the optional-tools positioning. Imports, workspace deps, configs, changeset config, examples, docs, and skills updated; lockfile regenerated.actureandeslint-plugin-acture-migrationkeep their already-published names. The 13 renamed packages are built/tested and ready to publish.Plan restructure
docs/roadmap.md(new) — forward plan + full done/not-done tracking.docs/next_session.md— next step is anacture-core positioning-alignment review. The v1.4-era handoff is parked indocs/backlog/.Test plan
pnpm build— all 15 packages buildpnpm test— 396 package tests greenpnpm typecheck— clean across all 15 packages@acture/references (remaining@acturementions are intentional prose about the rename).changeset/config.jsonvalid,fixedarray updated toacture-*names