@aayushchugh/skills 0.1.4 → 0.1.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@aayushchugh/skills",
3
- "version": "0.1.4",
3
+ "version": "0.1.5",
4
4
  "description": "The agent skills I use while building real products.",
5
5
  "author": "Ayush Chugh <hey@ayushchugh.com>",
6
6
  "license": "MIT",
@@ -1,9 +1,8 @@
1
1
  ---
2
2
  name: cases-to-run
3
3
  description: >-
4
- List cases to verify by hand, or name the code tests for no-slop when
5
- asked. Use when the user asks for test cases or to test a flow. Do not edit
6
- code or audit security.
4
+ Use when asked for test cases, QA coverage, or how to test a flow by hand.
5
+ Not for writing the test code or a security audit.
7
6
  ---
8
7
 
9
8
  # Cases to run
@@ -1,8 +1,8 @@
1
1
  ---
2
2
  name: go-or-stop
3
3
  description: >-
4
- Decide if a change is ready to ship, with a go or no-go, what to watch, and
5
- how to roll back. Use when the user asks for a release check. Do not deploy.
4
+ Use when asked if a change is ready to ship, or for a go or no-go. Not for
5
+ deploying.
6
6
  ---
7
7
 
8
8
  # Go or stop
@@ -1,9 +1,8 @@
1
1
  ---
2
2
  name: no-slop
3
3
  description: >-
4
- Write the smallest readable code that reuses existing code, installed
5
- utilities, and repo patterns, and fixes bugs at the root cause. Use when
6
- implementing, fixing, or reviewing code. Do not use for docs.
4
+ Use when writing or changing code, including a test that was asked for.
5
+ Not for docs, a review, or a design.
7
6
  ---
8
7
 
9
8
  # No slop
@@ -1,9 +1,8 @@
1
1
  ---
2
2
  name: one-shape
3
3
  description: >-
4
- Audit a repo for duplication, divergent flows, dead code, over-engineering,
5
- waste, and standards drift, then apply approved steps. Use when the user
6
- asks to refactor or clean up a codebase. Do not audit security.
4
+ Use when asked to refactor, clean up, or standardize a repo. Not for a
5
+ security audit or a single pull request.
7
6
  ---
8
7
 
9
8
  # One shape
@@ -1,9 +1,8 @@
1
1
  ---
2
2
  name: open-doors
3
3
  description: >-
4
- Review application code, APIs, dependencies, secrets, and deploy config for
5
- injection, web attacks, and DDoS controls. Use when the user asks for a
6
- security audit. Never attack a live target.
4
+ Use when asked for a security audit or a pentest-readiness review. Not for
5
+ a live attack or a normal code review.
7
6
  ---
8
7
 
9
8
  # Open doors
@@ -1,9 +1,8 @@
1
1
  ---
2
2
  name: plain-paper
3
3
  description: >-
4
- Write a spec or other documentation from the request, the code, and relevant
5
- sources. Use when the user asks for a PRD, spec, flow, API reference,
6
- runbook, guide, or README. Do not change code.
4
+ Use when asked for a PRD, spec, flow, API reference, runbook, guide, or
5
+ README. Not for code or a system design.
7
6
  ---
8
7
 
9
8
  # Plain paper
@@ -1,9 +1,8 @@
1
1
  ---
2
2
  name: red-pen
3
3
  description: >-
4
- Review a diff or pull request for bugs, regressions, broken callers, missing
5
- tests, and unmet requirements. Use when the user asks for a code review. Do
6
- not audit security, refactor, or write tests.
4
+ Use when asked to review a diff, a pull request, or a change. Not for a
5
+ security audit, a refactor, or writing tests.
7
6
  ---
8
7
 
9
8
  # Red pen
@@ -1,9 +1,8 @@
1
1
  ---
2
2
  name: the-cause
3
3
  description: >-
4
- Find a bug's root cause from the report, the code path, and the evidence.
5
- Use when the user asks to diagnose or debug a failure. Do not write the fix
6
- or the regression test.
4
+ Use when asked to diagnose, debug, or find why something fails. Not for
5
+ writing the fix or the test.
7
6
  ---
8
7
 
9
8
  # The cause
@@ -1,10 +1,8 @@
1
1
  ---
2
2
  name: the-map
3
3
  description: >-
4
- Map, propose, or improve a system's design like a senior engineer,
5
- grounding the recommendation in real usage and activity. Use when the user
6
- asks for a system design, architecture review, or scale or performance
7
- improvement. Do not write code.
4
+ Use when asked for a system design, an architecture review, or a scale or
5
+ performance improvement. Not for writing code or a PRD.
8
6
  ---
9
7
 
10
8
  # The map
@@ -1,8 +1,8 @@
1
1
  ---
2
2
  name: which-skill
3
3
  description: >-
4
- Pick and run the right skill, or a chain of skills, for a request. Use when
5
- unsure which skill applies or when a task spans several steps.
4
+ Use when a request could match more than one skill, or needs several skills
5
+ in a row.
6
6
  ---
7
7
 
8
8
  # Which skill