L
Lusona/ai-skills
Iterative product and engineering work with explicit outcomes, evidence, authorization, TDD, and bounded…
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"lusona-ai-skills": {
"command": "npx",
"args": ["skills@latest"]
}
}
}Parsed from the README we fetched on 2026-11-08; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"lusona-ai-skills": {
"command": "npx",
"args": ["skills@latest"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio lusona-ai-skills -- npx skills@latest
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 3 ★ · Lusona/ai-skills · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-09 · last seen 2026-11-14 · seen 6× · listed by 1 sources
- Score
- score 103 · 3 ★ · 1 sources · repo
- Install
npx skills@latest
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx skills@latest. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: Agent 技能. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
Lusona/ai-skills；first catalogued 2026-11-09；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# Lusona Skills
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
English | Español | Deutsch | 简体中文 | 日本語
Lusona organizes coding-agent skills around a shared work loop:
This is a common interaction loop. Start where needed and revisit steps as evidence changes.
Choose, act, check, repeat. Choose the next action from the outcome and current
evidence. Revisit exploration, investigation, design, implementation, or review as needed.
There is no fixed skill sequence.
Revise decisions as you learn. When evidence challenges an earlier decision, revisit
it within the agreed authority. Update affected records so subsequent work follows the
revised decision.
Continue within authorization. Resolve routine choices and keep working without
repeated approval. Ask when a decision exceeds existing authority.
Verify completion. Complete the agreed scope, required checks and review, and any
required acceptance or delivery. Report what remains when completion is blocked.
For Claude Code, Codex, Cursor, Xcode 27 coding agents, and Google Antigravity App, CLI, and IDE · Checked-out source version 2.0.1
> [!WARNING]
> Do not install Lusona using Vercel Skills (npx skills@latest); use the native plugin installation.
Read why we built Lusona Skills: Why we built Lusona Skills.
This README describes the source in this checkout. GitHub installation uses committed,
pushed sources; local changes do not establish a published release.
## Index
Where to start
Choose a command
Installation
How the work continues
Questions and evidence
Recovery and resumption
Results and handoffs
Reference
Contributing
License
Development
## Where to start
Start with status when joining a project, resuming work, or deciding what needs attention.
It assesses the available records and evidence, explains what remains, and recommends a next
action. It also works when the project has no Lusona records yet. Asking for status does
not authorize new implementation work.
For a new idea, explore helps examine possibilities and tradeoffs; frame-product helps
establish the users, problem, and product direction. As that direction becomes clearer,
map-capabilities identifies what the product needs to support and useful delivery order.
specify clarifies behavior and acceptance criteria; architect resolves consequential
technical decisions about boundaries, contracts, and ownership. design focuses on UI
mockups, screen flows, and diagrams; you can request it directly without another stage first.
implement carries an authorized change through execution and verification.
These are common ways work develops, not required stages. Start with the group that fits the
current need, skip settled questions, and return to any group when evidence calls for it.
Investigation can precede a specification or interrupt implementation; review can reveal a
reason to revisit a design.
| Action group | Skills and responsibilities |
| Orient | status: assess progress, remaining work, and the next useful action |
| Develop direction | explore: examine possibilities and tradeoffs frame-product: establish users, outcomes, and boundaries map-capabilities: map coverage, dependencies, and delivery order |
| Define a change | specify: agree on behavior, acceptance criteria, and TDD policy architect: resolve consequential technical decisions about boundaries, contracts, and ownership |
Lusona organizes coding-agent skills around a shared work loop:
This is a common interaction loop. Start where needed and revisit steps as evidence changes.
Choose, act, check, repeat. Choose the next action from the outcome and current
evidence. Revisit exploration, investigation, design, implementation, or review as needed.
There is no fixed skill sequence.
Revise decisions as you learn. When evidence challenges an earlier decision, revisit
it within the agreed authority. Update affected records so subsequent work follows the
revised decision.
Continue within authorization. Resolve routine choices and keep working without
repeated approval. Ask when a decision exceeds existing authority.
Verify completion. Complete the agreed scope, required checks and review, and any
required acceptance or delivery. Report what remains when completion is blocked.
For Claude Code, Codex, Cursor, Xcode 27 coding agents, and Google Antigravity App, CLI, and IDE · Checked-out source version 2.0.1
> [!WARNING]
> Do not install Lusona using Vercel Skills (npx skills@latest); use the native plugin installation.
Read why we built Lusona Skills: Why we built Lusona Skills.
This README describes the source in this checkout. GitHub installation uses committed,
pushed sources; local changes do not establish a published release.
## Index
Where to start
Choose a command
Installation
How the work continues
Questions and evidence
Recovery and resumption
Results and handoffs
Reference
Contributing
License
Development
## Where to start
Start with status when joining a project, resuming work, or deciding what needs attention.
It assesses the available records and evidence, explains what remains, and recommends a next
action. It also works when the project has no Lusona records yet. Asking for status does
not authorize new implementation work.
For a new idea, explore helps examine possibilities and tradeoffs; frame-product helps
establish the users, problem, and product direction. As that direction becomes clearer,
map-capabilities identifies what the product needs to support and useful delivery order.
specify clarifies behavior and acceptance criteria; architect resolves consequential
technical decisions about boundaries, contracts, and ownership. design focuses on UI
mockups, screen flows, and diagrams; you can request it directly without another stage first.
implement carries an authorized change through execution and verification.
These are common ways work develops, not required stages. Start with the group that fits the
current need, skip settled questions, and return to any group when evidence calls for it.
Investigation can precede a specification or interrupt implementation; review can reveal a
reason to revisit a design.
| Action group | Skills and responsibilities |
| Orient | status: assess progress, remaining work, and the next useful action |
| Develop direction | explore: examine possibilities and tradeoffs frame-product: establish users, outcomes, and boundaries map-capabilities: map coverage, dependencies, and delivery order |
| Define a change | specify: agree on behavior, acceptance criteria, and TDD policy architect: resolve consequential technical decisions about boundaries, contracts, and ownership |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/lusona-ai-skills/)
- Source
- github · https://github.com/Lusona/ai-skills
- Browse by field
- Agent skills
- Traction
- 3 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.