setup-lidessen-skills
Setup lidessen skills
Operational deployer for the lidessen skills collection. The lidessen methodology lives in the individual skills (harness, design-driven, goal-driven, reframe, evidence-driven, etc.); this skill does the wiring to land them in a target project — detect the host tool, write to the right harness file, and inject the cross-cutting principles that span multiple lidessen skills.
Position relative to harness
harness (and any general-purpose harness skill) teaches how to think about agent context — portable methodology, applies to any project regardless of skill collection. This skill is the lidessen-specific operational layer that applies harness-style structure to a project adopting the lidessen collection. Read harness for the why; run this skill to do the wiring.
Boundary — what this skill does and doesn't
Does:
- Detect host tool (Claude Code / Codex / Cursor / other) by config-file presence
- Create or update the project's harness config with a delimited "Lidessen" section
- Inject canonical cross-cutting principles from
references/cross-cutting-principles.md - Maintain a version marker so subsequent
sync/auditruns can detect drift
Doesn't:
- Teach lidessen methodology (each skill's own SKILL.md owns that)
- Copy or install skill files (use clone / symlink / your package manager)
More from lidessen/skills
memory
Manages cross-session knowledge persistence. Triggers on "remember", "recall", "what did we", "save this decision", "todo", or session handoff.
82design-driven
Design-driven development methodology — the design/ directory is the single source of architectural truth; read it before coding, stay within its boundaries, and update it first when the system's shape changes. Use whenever starting development on this project, or when the user asks to create/update architecture docs, add a feature that may cross existing boundaries, refactor system structure, or understand the codebase architecture. Triggers on "design first", "update the design", "does this change the architecture", "write a design for", "what's the current design", or onboarding to a codebase's shape. Args — `/design-driven init` to configure a project, `bootstrap` to generate design from existing code, `audit` to reconcile design/ against current code.
24harness
Agent harness architecture — structure a project's agent context across layers for effective AI-assisted development. Covers CLAUDE.md, skills, design docs, hooks, and all artifacts that shape how an agent understands and operates in a codebase. Use when setting up or improving agent configuration, when agent context feels bloated or disorganized, when onboarding a project for AI-assisted development, or when the agent keeps losing architectural awareness mid-task. Triggers on "set up claude", "improve CLAUDE.md", "agent keeps forgetting", "context is too long", "harness setup", "organize agent context", "how should I structure my prompts". Args — `/harness audit` to evaluate an existing project's context architecture, `init` to set up harness from scratch.
20housekeeping
Manages project housekeeping including documentation organization, dependency management, directory structure, code cleanup, technical debt tracking, and infrastructure configuration. Use when organizing documentation, cleaning up dependencies, reorganizing folders, removing dead code, addressing tech debt, or maintaining project structure.
18validation
Unified validation orchestration for code quality, consistency, and project health. Auto-triggers on code changes, PR creation, or explicit validation requests. Coordinates refining, housekeeping, and custom validators into cohesive pipelines. Use for "validate", "check", "verify", "验证", "检查", or when quality assurance is needed.
17orientation
Orients agents in new projects by scanning entry documents and discovering capabilities. Use at session start, when entering unfamiliar territory, or when asking "what can you do" or "where do I start".
16