Amo improve

Practical agent skills for real engineering workflows.

Install

npx -y skills add lencamo/skills --skill amo-improve

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when the user asks how to improve, extend, adjust, or redesign an existing feature or behavior before coding. Do not use for brand-new features, broken behavior, pure refactors, or second-pass solution challenges.

SKILL.md

2.8 KB, as published. Nobody here has run it

Amo Improve

Plan intentional changes to existing functionality without letting old implementation details decide the target design.

Shared Output Marker

Prefix the first output line inline with 🧰 [amo-improve]. Do not put the marker in a separate paragraph.

Use When

Current behavior exists, but the desired behavior is different.
The user wants to improve, extend, adjust, or redesign an existing feature.
The work may involve compatibility, migration, interaction changes, or touching existing modules.

Do Not Use

The behavior is entirely new; use amo-feature.
Existing behavior is wrong, broken, or unexpected; use amo-fix.
Structure is the primary problem with no behavior change; use amo-refactor.
A proposed solution needs challenge; use amo-best.

Best Standard

Select and state one before recommending a solution:

Target-state best: default for development-stage work when no explicit constraint is stated; prioritize correct boundaries, long-term maintainability, refactoring when needed, and not bending the design around legacy implementation.
Constraint best: use when the user requires fast delivery, compatibility, minimal change, short-term delivery, or limited scope.
Evolutionary best: use when the target design is right, but should be delivered in safe, staged steps.
Lowest-risk best: use when production, data, security, auth/permission, payment, migration, or rollback risk dominates.

Workflow

Identify current behavior and desired behavior.
Select the best standard and explain why.
Inspect implementation, ownership boundaries, and rendered behavior when UI is involved.
Decide whether to adapt existing code, reshape it, or stage the target design.
Recommend one approach with tradeoffs, blast radius, and verification.

Key Rules

Target behavior comes before preserving incidental implementation.
Do not add compatibility work unless the chosen best standard requires it.
Do not add speculative compatibility paths, fallback branches, or legacy handling without evidence from the codebase or explicit user requirements.
Keep unrelated cleanup out of scope.
If implementation reveals a better approach, pause and explain before switching.

Output

Use the user's language for output labels and content.

🧰 [amo-improve] Scenario: existing behavior change
Best standard:
Current behavior:
Target behavior:
Recommended approach:
Tradeoffs:
Impact scope:
Verification:
Next: use amo-best for second-pass pressure testing if needed