claudecodex

lnd-artifacts

Per-project AI artifact transport: keeps .claude/, openspec/, CLAUDE.md and friends in a private artifact repo cloned into the host project's git common dir, symlinked into the project root and never committed to the customer remote.

0 on GitHubby Lundegaardv0.3.0updated 1 month ago

Not in a marketplace yet, so it loads for one session with --plugin-dir.

Plugin lnd-artifacts in jankc/artifacts-store. Commands read from the repo's manifest — 28 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (12)

  • openspec-apply-change

    Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

  • openspec-archive-change

    Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

  • openspec-bulk-archive-change

    Archive multiple completed changes at once. Use when archiving several parallel changes.

  • openspec-continue-change

    Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

  • openspec-explore

    Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

  • openspec-ff-change

    Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

  • openspec-new-change

    Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

  • openspec-onboard

    Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

  • openspec-propose

    Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

  • openspec-sync-specs

    Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

  • openspec-verify-change

    Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

  • lnd-artifacts

    Manage this project's AI artifacts (.claude/, openspec/, CLAUDE.md, …) in a private artifact repository that is never committed to the customer repo. Use when the user wants to set up / initialize artifact management, adopt an existing artifact folder into the store, sync (commit + push) artifact ch

Slash commands (1)

  • /lnd-artifacts:help

    What lnd-artifacts is, this project's live artifact status, and the verbs it offers — AI artifacts in a private repo, never committed to the customer repo

Hooks (2)

  • SessionStart

    ${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh

  • Stop

    ${CLAUDE_PLUGIN_ROOT}/hooks/stop.sh

View source on GitHub

Maintain lnd-artifacts?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted