lidessen

@lidessen source repo

63 skills
0 followers
14 hours ago last updated

▌
Project Restructure 2 · lidessen bundle
Restructure and organize a repository through a staged campaign.

0
installs
▌
Agent Delegation 2 · lidessen bundle
Decide and operate bounded sub-agent contributions while one Main Agent retains the whole outcome, synthesis, and verification responsibility. Use when the user asks to use sub-agents, delegate, parallelize, form a swarm, or obtain an independent critic; when a non-trivial task contains independent investigations or disjoint implementation ownership; or when producer bias makes a fresh reviewer decision-relevant. Triggers include "use subagents", "delegate this", "parallel review", "多 Agent", "用 sub agent", "并行调查", and "找一个独立 reviewer". Do not use for a routine one-step task, to split coupled shared-state work among multiple writers, or as a replacement for a persistent orchestration runtime.

0
installs
▌
Practice Cycle 2 · lidessen bundle
Move a non-trivial task through practice, observation, reflection, and the next smallest test without forcing a generic plan or feedback artifact. Use when a phase ends, an implementation or investigation must inform its next move, a prior attempt failed or produced ambiguous evidence, work is being resumed, or the user asks to turn results into the next bounded action. Do not use as a mandatory preflight for routine one-step work or when a more specific methodology already owns the live judgment.

0
installs
▌
Agent Run · lidessen bundle
Run agents through a lightweight `agent-browser`-style CLI. Use when another agent needs `agent-run codex|cursor|claude-code|ai-sdk ...` as an immediate direct call, or local send/peek/wait sessions without depending on the daemon.

0
installs
▌
Perf · lidessen bundle
Run web UI performance tests for the agent-worker project. Automates build, daemon restart, cache-bust version bump, Lighthouse audit, and metric reporting — all in one command. Use this skill when the user says "run perf", "check performance", "lighthouse", "perf test", "why is it slow", "check TBT", "性能测试", "跑一下性能", or wants to measure/compare web UI performance. Also trigger after making changes to semajsx/style, render, or any web UI component when performance impact needs verification.

0
installs
▌
A2a Test · lidessen
Systematically test the @agent-worker/loop and @agent-worker/agent packages against real LLM backends using the aw CLI. A2A tests are interactive, CLI-driven tests — not automated TS scripts. Use this skill when the user asks to test loops, run a2a tests, verify runtime implementations, or check if agent loops work correctly. Trigger on phrases like 'test loops', 'run a2a tests', 'test the runtimes', 'verify loop implementations', 'check if claude/codex/cursor works'.

0
installs
▌
Dev Eval · lidessen
Run comparative development evaluations: assign the same task to agent-worker team AND claude-code (team subagents), then have an evaluator agent score both and a reviewer agent verify the evaluation. Fully orchestrated — you coordinate all phases, agents notify via channel/callback when done. Use this skill when the user wants to benchmark agent-worker vs claude-code, run a dev eval, compare agent performance, or prove that the workspace team outperforms solo agents. Trigger on phrases like 'dev eval', 'run eval', 'compare performance', 'benchmark', '对比评估', '开发评估', '跑评估', 'eval iteration', '/dev-eval'.

0
installs
▌
Gen Test · lidessen
Generate unit tests for a given module using bun:test conventions and existing test patterns. Use when the user asks to generate tests, add test coverage, or create a test file. Trigger on phrases like 'gen test', 'generate tests', 'add tests for', 'write tests', 'test coverage'.

0
installs
▌
Attention Driven · lidessen bundle
Use go/setup/audit/goal/design/fact/reframe/close as the stable entrypoint for ordinary agent work. Use when starting or resuming work, choosing autonomous action vs review vs escalation, changing system shape, recording progress, verifying claims, or closing work with a durable record.

0
installs
▌
Code Check · lidessen
Run code quality checks: formatting (oxfmt), linting (oxlint), and type checking (tsgo). Automatically fix issues when possible, but only apply fixes that are semantically correct — never suppress errors, add meaningless type casts, or degrade code quality just to pass checks. Trigger on phrases like 'code check', 'check code', 'run checks', 'lint and format', 'typecheck'.

0
installs
▌
Prompt Craft · lidessen
Write and improve agent prompts using tested principles from Anthropic's constitution, prompt lab experiments, and identity-driven design. Use when creating system prompts, workspace agent instructions, soul definitions, or improving existing prompts. Trigger on phrases like 'write prompt', 'improve prompt', 'craft prompt', 'agent instructions', 'system prompt', 'agent personality'.

0
installs
▌
Agent Workspace · lidessen
Monitor, inspect, and interact with the agent workspace using the agent-workspace MCP tools. Use this skill when the user wants to check agent status, read workspace channels, send messages to agents, view event logs, inspect the instruction queue, or test how agents behave in the workspace. Trigger on phrases like 'check agents', 'workspace status', 'send message to agents', 'what are agents doing', 'test agent behavior', 'debug workspace', 'monitor agents', 'read channel', 'check queue'.

0
installs
▌
Dive · lidessen bundle
Dives deep into project questions using layered investigation (docs → code → analysis) to provide evidence-based answers with file:line citations. Use when asking "how does X work", "what is Y", "where is Z", or investigating features, APIs, configuration, codebase structure, or technical decisions.

0
installs
▌
Setup · lidessen
Bootstrap agent working system for a new project. Triggers on "setup agent system", "initialize claude", "bootstrap project".

0
installs
▌
Memory · lidessen bundle
Manages cross-session knowledge persistence. Triggers on "remember", "recall", "what did we", "save this decision", "todo", or session handoff.

0
installs
▌
Refining · lidessen bundle
Refines code changes for better reviewability. Validates change cohesion (no mixed concerns), generates clear commit messages, creates PR/MR with reviewer-focused descriptions. Use when committing, reviewing, creating PR/MR, or mentions "commit", "review", "PR", "MR", "pull request", "merge request", "refine", "提交", "审查".

0
installs
▌
Agent E2e · lidessen bundle
Discover, record, and execute E2E test cases using browser exploration. Use when exploring test scenarios, recording user flows, organizing test structure, or executing YAML-based tests.

0
installs
▌
Prompt Lab · lidessen bundle
Test, validate, and improve agent instructions (CLAUDE.md, system prompts) using sub-agents as experiment subjects. Measures instruction compliance, context decay, and constraint strength. Use for "test prompt", "validate instructions", "prompt effectiveness", "instruction decay", or when designing robust agent behaviors.

0
installs
▌
Validation · lidessen bundle
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.

0
installs
▌
Engineering · lidessen bundle
Guides technical decisions, architecture, and implementation. Use for tech choices, system design, API design, refactoring, or "how should I build this" questions.

0
installs
▌
Orientation · lidessen bundle
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".

0
installs
▌
Agent Worker · lidessen bundle
Create and manage AI agent sessions with multiple backends (SDK, Claude CLI, Codex, Cursor). Also supports multi-agent workflows with shared context, @mention coordination, and collaborative voting. Use for "start agent session", "create worker", "run agent", "multi-agent workflow", "agent collaboration", "test with tools", or when orchestrating AI conversations programmatically.

0
installs
▌
Housekeeping · lidessen bundle
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.

0
installs
▌
Frontend Init · lidessen
Initialize frontend projects with opinionated modern toolchain - Bun (package manager), Oxfmt (formatter), Oxlint (linter), tsdown (npm bundler), tsgo (type checker). Use when creating new frontend/TypeScript projects, setting up project tooling, or mentions "init project", "new frontend", "setup tooling".

0
installs
▌
Authoring Skills · lidessen bundle
Guide for authoring effective Agent Skills using principle-based approach (Progressive Disclosure, Respect Intelligence, Enable Discovery). Covers creating, improving, refactoring, and reviewing skills. Use for skill authoring, design questions, best practices, anti-patterns, or structure decisions.

0
installs
▌
Dogfood · lidessen bundle
Use as the local-Rossovia dogfood mode of the broader rossovia-development Skill when Rossovia itself should resolve, modify, verify, rebuild, restart, observe, and roll back a named project. It is a compatibility entry for "dogfood", "自我改进", "让 Rossovia 修改自己", and similar requests; use rossovia-development when local dogfood is unavailable and an external harness must delegate the work.

0
installs
▌
Code Review · lidessen bundle
Review a proposed code change, staged diff, commit, patch, or pull request for decision-changing defects before acceptance or merge. Use when asked "review this code", "review the diff/PR", "can this merge", "find regressions", or when a consequential implementation needs an impact-aware independent review. Do not use to implement the change, process already-filed PR comments, settle an unaccepted architecture, review visual design, or orchestrate reviewers.

0
installs
▌
Task Shaping · lidessen bundle
Judge a consequential task against a conservative Flash-class reference execution profile, then choose direct execution, guarded verification, or a transformation of oversized, branchy, long-context, weakly observable, or completeness-sensitive work into locally verifiable units that can be reconstructed without losing global constraints. Use when deciding one agent versus bounded Cells, an agent loop varies or misses obligations, a verifier skips claims despite seeing evidence, a task needs semantic decomposition before orchestration, a harness needs a dependable task primitive, or asking "can an agent reliably do this?", "how should this task be split?" / "任务怎么拆才能稳定" / "稳定能力包络". Do not use for ordinary one-step planning, proving a model capability without repeated evidence, choosing provider/concurrency/budget, executing a prepared queue, or replacing a domain skill that already owns the semantic partition.

0
installs
▌
Agent Tooling · lidessen bundle
Operate and tune the tool layer around coding agents such as Codex, Claude Code, and Cursor. Use when an agent must run a harness interactively or headlessly, select structured output and permissions, inspect the effective skills, hooks, MCP servers, plugins, rules, memories, or tools, cache version-specific capability evidence, compare normal and lean profiles, or remove tooling that makes agent work worse. Also use for requests about codex exec, claude -p, cursor-agent -p, coding-agent CLI automation, or agent setup bloat. Do not use for raw model API integration, multi-agent orchestration, portable cross-device setup, or a project workflow problem whose owning surface is still unknown.

0
installs
▌
Form Guidance · lidessen bundle
Decide the smallest truthful form for a repeated problem before designing its implementation: no new artifact, local instruction, durable decision record, skill, runtime, projection, or bounded campaign. Use when asking "should this be a skill?", "what form should this take?", "how should this capability exist?", "is this another agent/runtime?", "should we add a command or document?", or when a generic workflow would hide an authority, inheritance, or recurrence decision. Do not use for ordinary implementation after the form is already accepted.

0
installs
▌
Visual Design · lidessen bundle
Design, redesign, refine, or review real interfaces, documents, illustrations, and visual systems from their content, audience, intended action, and project direction. Use when creating UI, improving visual hierarchy or coherence, reviewing a rendered artifact, establishing a continuing project's direction from references, translating an ambiguous style cue into provisional guidance, or applying an accepted direction to code without reopening taste. Triggers include "design/redesign/review the UI", "the page works but feels generic/inconsistent", "the direction is right but components feel generic", "polish/refine interface details", "align logo or illustration with product", "apply the selected style", "art direction", and "审美/视觉设计/组件细节/插画或品牌视觉统一/确立风格/按现有风格落实". Do not use for purely functional fixes, naming, or automatic aesthetic acceptance. Never impose a portable fixed style.

0
installs
▌
Visualization · lidessen bundle
Use a source-linked Project Lens to introduce the current state of a real repository or explain change impact against an explicit base revision. Use when asked to "visualize/explain this repo", "show current project state", "show what changed by responsibility", "用可视化介绍这个项目", "展示项目现状", or "按责任解释这次变更" and the host provides the human-agent-visualization Project Lens capability. Do not use for generic UI design, a decorative dependency graph, durable project cognition, or a claim that directory structure is accepted architecture.

0
installs
▌
Practice Cycle · lidessen bundle
Move a non-trivial task through practice, observation, reflection, and the next smallest test without forcing a generic plan or feedback artifact. Use when a phase ends, an implementation or investigation must inform its next move, a prior attempt failed or produced ambiguous evidence, work is being resumed, or the user asks to turn results into the next bounded action. Do not use as a mandatory preflight for routine one-step work or when a more specific methodology already owns the live judgment.

0
installs
▌
Reframe · lidessen bundle
Designing in territory where the industry is still groping for shape — AI-native systems, agent-first interfaces, any domain whose category is forming. Triggers on "AI native X", "agent-first X", "redefine X", "rebuild X from scratch under Y", "reframe X for Y", "what should X look like in the new paradigm", "design a system with no precedent", or the tension between "new shoes on the old path" and "a skeleton that holds on its own". Method — strip to 3-5 abstract functions, redraw the load-bearing skeleton from the new paradigm's primitives, stress-test without traditional crutches, then add familiar flesh as projection. Do NOT trigger for incremental redesigns within an existing paradigm (use design-driven), explanatory writing (use technical-article-writing), or vague "make it AI" requests. Pairs with design-driven (upstream) and goal-driven (parallel). Args — `/reframe init`, `close`, `explain [for <audience>]`.

0
installs
▌
Work Estimation · lidessen bundle
Estimate the necessary work before converting it into agent tokens, time, or money. Use when comparing implementation options, setting an agent budget, choosing estimate granularity or error tolerance, planning a discovery probe, or asking "how much work is this really?" / "预算怎么估？" / "工作量评估" / "误差容忍度". Do not use to invent a token price, approve spend, or replace strategic choice, execution, or calibration evidence.

0
installs
▌
Agent Delegation · lidessen bundle
Decide and operate a portable one-Main/many-child working mode while the Main Agent retains the whole outcome, synthesis, and verification responsibility. Use when the user asks to use sub-agents, delegate, parallelize, form a swarm, coordinate several explicit Runs, or obtain an independent critic; when a non-trivial task contains independent investigations or disjoint implementation ownership; or when producer bias makes a fresh reviewer decision-relevant. Map the same semantic work units to the active harness, including native sub-agents in Codex-class tools or an injected sub-worker capability backed by explicit persistent Runs in Rossovia-class runtimes. Triggers include "use subagents", "one main many children", "delegate this", "parallel review", "一主多子", "多 Agent", "用 sub agent", "多 Run 编排", "并行调查", and "找一个独立 reviewer". Do not use for a routine one-step task, to split coupled shared-state work among multiple writers, or to create a second lifecycle beside the active runtime.

0
installs
▌
Document Writing · lidessen bundle
Write, rewrite, or audit truthful prose for a real document, reader, and purpose without reducing quality to an anti-AI phrase list. Use for READMEs, design and decision documents, reports, explainers, guides, essays, internal notes, public project copy, or requests such as "write this document", "rewrite this README", "make this sound less AI-generated", "好好表达", "去 AI 味", "改写文档", and "这段话写得不像人". Do not use for choosing a shared name, visual layout, literal transcription, or mechanical formatting.

0
installs
▌
Model Evaluation · lidessen bundle
Build or revise an evidence-linked capability profile for a model execution setup by running repeated, representative real tasks under matched conditions. Use when comparing models, providers, plans, coding harnesses, or prompt/tool profiles for task allocation; when asking "which model is good enough for this work?", "evaluate this model", "compare model capability", "模型评测/能力画像/模型适合什么任务", or whether a characterized setup may have degraded. Do not use for provider setup, public leaderboard summaries, one-off response review, automatic routing, or a degradation verdict without an accepted baseline.

0
installs
▌
Agent Environment · lidessen bundle
Use this Skill, not a named task Skill, when that Skill or capability is the object of user-level setup, installation, migration, or configuration. An installed or runtime-discovered copy is target evidence, not a desired source. If the human has not supplied the selected capability's source, return `NEEDS_INPUT` before reading it, inventory, lookup, planning, or action; never inspect secret values. Use for "set up my agents on this machine", "migrate my AI coding setup", "新设备配置 Codex/Cursor/Claude Code", "update my global agent workflow", or reconstructing selected skills, harness guidance, plugins, MCP, hooks, permissions, runtimes, and authentication prerequisites. Setup does not imply marketplace discovery, CLI/provider installation, or full-toolbox adoption. Do not use for project-local agent workflow design, fleet policy, sessions/caches, or unrelated dotfiles.

0
installs
▌
Project Cognition · lidessen bundle
Build, verify, or selectively refresh a source-linked working model of a substantial project when later agents or tasks need to reuse its architecture, responsibilities, authority, state, causal, evidence, or change relations. Use for "initialize project cognition", "map this project for future work", "建立项目认知", "更新项目认知", "what existing cognition is invalidated by this change?", or when repeated tasks keep reconstructing the same project model. Do not use for a one-off code review, ordinary repository orientation, context-delivery configuration, or as a mandatory project setup step.

0
installs
▌
Skill Engineering · lidessen bundle
Design, rewrite, review, and test agent skills that improve a repeated agent action or judgment. Use when creating a skill, rewriting a SKILL.md, improving a known skill trigger or action layer, reducing skill-context bloat, or checking whether a skill instruction actually changes behavior. Triggers include "create a skill", "rewrite this skill", "review this SKILL.md", "improve this project skill", "skill design", and "test this skill prompt". If an agent-work failure has not yet been localized to a skill, let an agent-workflow diagnostic method identify the owning surface first.

0
installs
▌
Strategic Advisory · lidessen bundle
Prepare an evidence-backed strategic recommendation when a project phase has settled, material conditions changed, or a human asks for short-, medium-, and long-horizon direction. Synthesizes verified phase evidence into a proposed Strategy Case with a principal contradiction, strongest preservation case, rolling horizons, mission candidates, and replan signals. It advises only: humans approve commitments, and Work Cells or other owners execute them. Do not use for ordinary task planning, implementation sequencing, or automatic portfolio management.

0
installs
▌
Goal Driven · lidessen bundle
Goal-driven methodology for multi-week initiatives where the destination is clearer than the path — GOAL.md as stable compass (General Line plus falsifiable success criteria), record captures what was tried and observed. Triggers on "set a goal", "track my progress on X", "this is exploratory", "I know the goal but not the path", or starting a months-long initiative without a clear technical shape. Use for research, exploratory features, learning projects with a shippable output, book/article series, job search, side-business launches. Do NOT trigger for single-task work, bug fixes, week-long features with a clear plan, vague aspirations ("be healthier"), habit tracking, or general life management. Pairs with design-driven (why/how-far vs what-shape) and runs parallel to reframe. Args — `/goal-driven set`, `review`, `close`.

0
installs
▌
Context Engineering · lidessen bundle
Design, audit, and verify how decision-relevant project information reaches an agent through the actual runtime. Use when an agent misses a governing boundary, receives irrelevant context, cannot discover an instruction or skill, or when deciding what should be always available, activated for a task, or retrieved on demand. Do not use to author domain knowledge, organize its source artifacts, write a one-off prompt, configure vendor hooks, or build an agent runtime.

0
installs
▌
Systems Engineering · lidessen bundle
Design or revise a sufficiently reliable whole from fallible human, Agent, software, and organizational parts under concrete constraints and accepted residual risk. Use when a workflow keeps failing despite locally reasonable tasks, when deciding where verification, redundancy, retries, rollback, budget margin, or human acceptance belong, when a Swarm or multi-stage Agent process needs an end-to-end reliability model, when component quality is being confused with system quality, or when asking "how can unreliable agents form a reliable system?", "where should the feedback loop close?", "怎么把会犯错的 Agent 组成可靠系统?" / "如何从流程上保证近似可靠?". Do not use for an ordinary bounded task, generic planning, proving model capability, converting work into token/time/cost estimates, or operating an already prepared queue.

0
installs
▌
Attention Management · lidessen bundle
Restore and maintain the governing relation for an Agent's next action when a long task drifts into a local branch, a correction changes assumptions, a phase transition buries the mainline, or recurring reminders, role-entry, or prompt habits need evaluation. Use for "manage agent attention", "return to the mainline", "attention drift", "保持主线", "注意力管理", "提示词衰退", or when the governing relation has drifted and a branch needs retention, return, reset, or reform judgment. Do not use to author doctrine, plan an entire project, configure vendor hooks, or infer neural activation from behavioral output.

0
installs
▌
Rossovia Development · lidessen bundle
Use when an Agent or external harness must develop Rossovia itself or a named project through Rossovia's capabilities. It chooses between local Rossovia dogfood and external-harness delegation, keeps one write owner, supplies receiver-specific main/worker/reviewer prompts, and closes the loop through verification, rebuild/restart, observation, and rollback. Triggers include "develop Rossovia", "改进 Rossovia", "自我开发", "dogfood", "修一下项目", "用 Rossovia 修改自己", "重要设计多轮迭代", and "并行研究后综合".

0
installs
▌
Design Driven · lidessen bundle
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.

0
installs
▌
Artifact Organization · lidessen bundle
Audit whether a project's artifact layout still expresses its accepted design, then apply one smallest safe organization transition when a material gap exists. Use for "organize the repo", "组织架构", "根据地", stale project structure, source/projection confusion, or campaign residue. Not for ordinary file cleanup, system-module design, Sequence change, or skill authoring.

0
installs
▌
Principle Cultivation · lidessen bundle
Steward a project's fallible principle lineage: preserve source-bound research, turn only gate-passing inquiries into candidates, convene selective P-ID reviews, clarify interpretations, trial human-nominated alternates, and prepare human-only Sequence decisions. Use for reusable-principle research, candidate proposals, principle reviews, interpretation drift, alternate trials, or maintaining a principle-centered skill collection.

0
installs
▌
Improve Agent Workflow · lidessen bundle
Diagnose and improve how coding agents work in an existing project: project skills, AGENTS instructions, prompt and context delivery, tools or CLI surfaces, hooks, verification, handoffs, and agent-facing workflow. Use when an agent repeatedly misses scope or instructions, the owning agent-facing surface is unclear, several surfaces interact, agent experience is costly or confusing, or a user asks Codex to improve how agents work in a company repository. Also use when the owning surface is a tool or CLI contract: to review, audit, fix, or improve a CLI's commands, arguments, help, output, or how agents invoke it from a shell. Triggers include "review this CLI", "audit the command interface", "make this CLI agent-friendly", "CLI/命令/参数审查", and agent invocation ergonomics. Start from observed project evidence, change the smallest owning surface, and verify behavior through the ordinary agent entry path. If the issue is already localized to a skill's trigger, prompt, context layering, or behavior evaluation and a

0
installs
▌
Product Dogfood Review · lidessen bundle
Review a real running product from the user's point of view by inventorying its pages and states, completing representative tasks in a supplied browser, and returning a traceable, decision-sized review packet. Use when asked to "dogfood the product", "review every page from a user's perspective", "全面 review 页面/流程", or "从使用角度检查 UI". Do not use for a visual-contract or aesthetic review alone, source-level code review, accessibility/performance audit alone, implementation, worker topology, or merge authority.

0
installs
▌
Structural Refactoring · lidessen bundle
Analyze, plan, execute, and verify behavior-preserving structural code changes. Use when asked to refactor code across meaningful boundaries: split a large file or module, extract responsibilities, untangle dependencies, reorganize a package, migrate callers, or assess the impact of a consequential refactor. Do not use for routine local cleanup, feature work that intentionally changes behavior, project artifact organization, or an unsettled architecture choice.

0
installs
▌
Evidence Driven · lidessen bundle
Evidence-driven methodology for the execution layer — every claim of progress requires a falsifiable observation; "looks right to me" is rejected. Use for production code, regression-prone systems, or any task where build-time discipline materially affects outcome quality. Triggers on "set up TDD", "build discipline", "no progress without evidence", "test-first", "verify rigorously", "production code workflow". Do NOT trigger for prototypes, exploratory spikes, throwaway scripts, or doc-only changes. Pairs with design-driven (which defines what to verify; evidence-driven defines how) — each works alone. Args — `/evidence-driven init` to wire up agent configs and optional pre-commit hooks. No periodic-audit command; it's an always-on overlay.

0
installs
▌
Writing Profile · lidessen bundle
Writer voice profile — an MBTI-inspired adaptive assessment that captures a person's cross-genre writing taste and style preferences. Use when the user wants to build or update their writing profile, calibrate AI writing tools to their voice, or find out "what kind of writer am I". Triggers on phrases like "写作画像", "writing profile", "writer type", "我是什么类型的作者", "测一下我的写作风格偏好", "calibrate my writing voice", or any explicit mention of building a writer profile. Produces a file at `~/.claude/writing-profile/profile.md` that downstream writing skills (technical-article-writing, future blog/diary skills) read to adapt AI output to the user's voice.

0
installs
▌
Disciplined Development · lidessen bundle
Lightweight behavioral discipline for any development task — ground decisions in evidence, choose the smallest valid change, test before claiming done, and analyze the specific situation before applying a pattern. Triggers on "be more disciplined", "professional habits", "stop overengineering", "check your work", "don't guess", "bad habits", "test strategy", "meaningful tests", or "avoid test bloat"; also when an agent shows overconfidence, untested claims, or repetitive overengineering across tasks.

0
installs
▌
Mechanism Design Review · lidessen bundle
Review proposed mechanisms in agent harnesses, agent runtimes, orchestration, workflows, and agent-facing infrastructure before implementation. Use when a design adds state, records, queues, locks, retries, gates, hooks, registries, protocols, lifecycle stages, daemons, or approval flows; when asking whether a prompt, Skill, policy, or existing owner is sufficient; or when defensive controls are making the system longer and more complex; when verification, review, acceptance, retry, continuation, or recovery meanings are being conflated; when an action vocabulary keeps growing; or when a mechanism or architecture review must give a design owner a self-contained working model and decision rather than a list of code links and findings. Do not use for ordinary implementation of an already accepted mechanism or for code-level defect review.

0
installs
▌
Naming And Articulation · lidessen bundle
Choose and place a project, product, or concept name with its smallest useful definition and explanation. Use when naming a project or shared concept, defining terminology, clarifying status words, deciding where documentation belongs, or asking "what should we call this?" / "how should this be explained?" / "命名" / "术语" / "定义" / "说明". Do not use for branding, ordinary copyediting, one-off prose, or a Sequence change.

0
installs
▌
Article Refactor · lidessen
Refactoring existing articles or drafts using a code-refactoring metaphor — extract information units (facts, claims, examples, metaphors) into a neutral inventory, rewrite the skeleton for a new thesis or audience, then inline units with expansion, compression, or transformation. Triggers on "重构这篇文章", "把这几篇合并改写", "用这些素材重写一篇", "这篇骨架我想换但素材想保留", "把旧博客整理重写", "refactor this article", "restructure this draft". Use to restructure existing pieces, merge drafts, repurpose for a different audience, or salvage old writing. Do NOT trigger for writing from scratch (use technical-article-writing) or light polish (use technical-article-writing's `revise`).

0
installs
▌
Project Restructure · lidessen bundle
Restructure a repository or workspace carrier when accepted design has moved ahead of legacy layout — inventory concrete state, derive a functional map, plan minimal retire/merge/regenerate waves, and verify hard constraints after each slice. Triggers on "整理项目", "清理旧内容", "restructure the repo", "retire legacy paths", "repo cleanup", "carrier refactor", "保留新设计清理旧的", "project housekeeping after regeneration". Use after target architecture or design truth exists; not for unsettled paradigm exploration or Sequence change. Args — inventory, plan, execute, verify.

0
installs
▌
Setup Lidessen Skills · lidessen bundle
Operational deployer for the lidessen skills collection — wires harness config (CLAUDE.md / AGENTS.md / .cursor/) in a target project, injects an L1 expression of selected sequence principles, and reconciles when lidessen evolves. Triggers on "/setup-lidessen-skills", "set up lidessen skills", "wire lidessen into this project", "sync lidessen principles", "install lidessen skills". Use after cloning or symlinking lidessen skills into a project, when adopting the collection, or when lidessen has new content the project hasn't picked up. Args — `init` to scaffold, `sync` to re-align with current lidessen, `audit` to check drift without writing. Pairs with harness (portable methodology); this is the lidessen-specific application layer.

0
installs
▌
Iterative Product Improvement · lidessen bundle
Run bounded, multi-round improvement of a real product or UI: observe a representative user task, decide whether a complex page or surface is necessary, choose the smallest useful change, implement it through the owning skill, and verify the changed experience in the browser before selecting the next practice. Use when asked to "多轮走查", "迭代改进 UI", "全面检查页面并持续修复", "这个复杂页面是否有必要", or to continue from an earlier product review. Do not use for a single read-only product review, visual direction formation alone, or implementation without live product evidence.

0
installs
▌
Technical Article Writing · lidessen bundle
Methodology for writing argumentative technical articles — pieces that convince the reader of a specific claim through a chain of reasoning. Use when the user wants a technical article, essay, or book chapter that takes a position — introducing a new idea, challenging an accepted one, or arguing for a particular approach. Triggers on phrases like "write an article/essay/chapter about X," "make the case for X," "argue that Y," or structuring a multi-chapter argument about agents, architectures, systems design, or methodology. Do NOT trigger for tutorials ("how to do X"), reference or API documentation, release notes, changelogs, or pure explainers where no claim is being argued — those need a different framework.

0
installs

63 published skills