agents-templated 2.2.10 → 2.2.12
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/README.md +100 -86
- package/agents/commands/README.md +64 -0
- package/agents/commands/SCHEMA.md +22 -0
- package/agents/commands/arch-check.md +58 -0
- package/agents/commands/audit.md +58 -0
- package/agents/commands/debug-track.md +58 -0
- package/agents/commands/docs.md +58 -0
- package/agents/commands/fix.md +58 -0
- package/agents/commands/learn-loop.md +58 -0
- package/agents/commands/perf.md +58 -0
- package/agents/commands/plan.md +58 -0
- package/agents/commands/pr.md +58 -0
- package/agents/commands/problem-map.md +58 -0
- package/agents/commands/release-ready.md +58 -0
- package/agents/commands/release.md +58 -0
- package/agents/commands/risk-review.md +58 -0
- package/agents/commands/scope-shape.md +58 -0
- package/agents/commands/task.md +58 -0
- package/agents/commands/test.md +58 -0
- package/agents/commands/ux-bar.md +58 -0
- package/agents/rules/planning.mdc +69 -0
- package/bin/cli.js +116 -4
- package/index.js +12 -1
- package/lib/workflow.js +177 -0
- package/package.json +2 -1
- package/templates/CLAUDE.md +5 -0
- package/templates/README.md +103 -61
- package/templates/agents/commands/README.md +43 -3
- package/templates/agents/commands/arch-check.md +58 -0
- package/templates/agents/commands/audit.md +58 -38
- package/templates/agents/commands/debug-track.md +58 -0
- package/templates/agents/commands/docs.md +58 -34
- package/templates/agents/commands/fix.md +58 -34
- package/templates/agents/commands/learn-loop.md +58 -0
- package/templates/agents/commands/perf.md +58 -34
- package/templates/agents/commands/plan.md +58 -34
- package/templates/agents/commands/pr.md +58 -35
- package/templates/agents/commands/problem-map.md +58 -0
- package/templates/agents/commands/release-ready.md +58 -0
- package/templates/agents/commands/release.md +58 -39
- package/templates/agents/commands/risk-review.md +58 -0
- package/templates/agents/commands/scope-shape.md +58 -0
- package/templates/agents/commands/task.md +58 -35
- package/templates/agents/commands/test.md +58 -34
- package/templates/agents/commands/ux-bar.md +58 -0
- package/templates/agents/skills/README.md +15 -0
- package/templates/agents/skills/debug-skill/SKILL.md +39 -0
- package/templates/agents/skills/emilkowalski-skill/SKILL.md +51 -0
- package/templates/agents/skills/feature-forge/SKILL.md +39 -0
- package/templates/agents/skills/raphaelsalaja-userinterface-wiki/SKILL.md +51 -0
- package/templates/agents/skills/secure-code-guardian/SKILL.md +39 -0
- package/templates/agents/commands/refactor.md +0 -34
- package/templates/agents/commands/scaffold.md +0 -34
|
@@ -0,0 +1,51 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: raphaelsalaja-userinterface-wiki
|
|
3
|
+
description: UI and UX best-practice playbook for stronger information architecture, readability, and usability.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# User Interface Wiki Playbook
|
|
7
|
+
|
|
8
|
+
Use this skill when improving UI clarity, hierarchy, and interaction ergonomics.
|
|
9
|
+
|
|
10
|
+
## Trigger Conditions
|
|
11
|
+
|
|
12
|
+
- User requests a frontend cleanup or UX review.
|
|
13
|
+
- Interface has weak visual hierarchy or navigation confusion.
|
|
14
|
+
- Product needs consistent UI patterns across pages.
|
|
15
|
+
|
|
16
|
+
## Workflow
|
|
17
|
+
|
|
18
|
+
1. Audit hierarchy: headings, spacing, grouping, and contrast.
|
|
19
|
+
2. Audit navigation and task flow for top user goals.
|
|
20
|
+
3. Standardize component patterns (cards, forms, tables, dialogs).
|
|
21
|
+
4. Tighten copy and labels for faster comprehension.
|
|
22
|
+
5. Validate responsive behavior at mobile, tablet, and desktop widths.
|
|
23
|
+
6. Validate accessibility semantics and keyboard flow.
|
|
24
|
+
|
|
25
|
+
## Interface Quality Checklist
|
|
26
|
+
|
|
27
|
+
- Primary action is obvious in each view.
|
|
28
|
+
- Navigation labels are unambiguous.
|
|
29
|
+
- Form errors are clear, contextual, and actionable.
|
|
30
|
+
- Empty/loading/error states are explicit.
|
|
31
|
+
- Density and spacing are consistent across sections.
|
|
32
|
+
|
|
33
|
+
## Output Contract
|
|
34
|
+
|
|
35
|
+
- UX issues grouped by severity
|
|
36
|
+
- IA and layout improvements
|
|
37
|
+
- Component consistency decisions
|
|
38
|
+
- Accessibility and responsiveness findings
|
|
39
|
+
- Validation steps and acceptance criteria
|
|
40
|
+
|
|
41
|
+
## Guardrails
|
|
42
|
+
|
|
43
|
+
- Avoid visual changes that break existing design-system tokens.
|
|
44
|
+
- Keep interaction patterns predictable and learnable.
|
|
45
|
+
- Optimize for readability before decoration.
|
|
46
|
+
- Confirm improvements with at least one critical user journey.
|
|
47
|
+
|
|
48
|
+
## Upstream Reference
|
|
49
|
+
|
|
50
|
+
- Original package command:
|
|
51
|
+
- npx skills add raphaelsalaja/userinterface-wiki
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: secure-code-guardian
|
|
3
|
+
description: Enforces secure-by-default implementation for auth, credentials, and untrusted input paths with OWASP-aligned controls.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Secure Code Guardian
|
|
7
|
+
|
|
8
|
+
Use this skill when building or reviewing features that touch authentication, secrets, session logic, or user-controlled input.
|
|
9
|
+
|
|
10
|
+
## Trigger Conditions
|
|
11
|
+
|
|
12
|
+
- User asks for secure implementation, auth, JWT, password handling, or OWASP checks.
|
|
13
|
+
- New endpoints, forms, or integrations expose untrusted input boundaries.
|
|
14
|
+
- A feature handles sensitive data, identity, or permissions.
|
|
15
|
+
|
|
16
|
+
## Workflow
|
|
17
|
+
|
|
18
|
+
1. Map trust boundaries, actors, and attack surface.
|
|
19
|
+
2. Define authentication and authorization requirements.
|
|
20
|
+
3. Apply input validation and injection defenses at boundaries.
|
|
21
|
+
4. Enforce credential/secrets handling and safe logging rules.
|
|
22
|
+
5. Add abuse protection controls (rate limiting, lockouts, replay defenses where relevant).
|
|
23
|
+
6. Define security tests and residual risk before ship recommendation.
|
|
24
|
+
|
|
25
|
+
## Output Contract
|
|
26
|
+
|
|
27
|
+
- Attack surface map
|
|
28
|
+
- Security requirements
|
|
29
|
+
- Applied controls by boundary
|
|
30
|
+
- OWASP alignment notes
|
|
31
|
+
- Security validation checklist
|
|
32
|
+
- Residual risks and mitigations
|
|
33
|
+
- Ship/block recommendation
|
|
34
|
+
|
|
35
|
+
## Guardrails
|
|
36
|
+
|
|
37
|
+
- Never trust client-side validation alone.
|
|
38
|
+
- Never expose secrets, credentials, or sensitive payloads in logs.
|
|
39
|
+
- Block release recommendation if critical controls are missing.
|
|
@@ -1,34 +0,0 @@
|
|
|
1
|
-
# /refactor
|
|
2
|
-
|
|
3
|
-
## A. Intent
|
|
4
|
-
Improve internal structure without changing externally observable behavior.
|
|
5
|
-
|
|
6
|
-
## B. When to Use
|
|
7
|
-
Use for maintainability and modularity improvements.
|
|
8
|
-
|
|
9
|
-
## C. Required Inputs
|
|
10
|
-
- Target component/module
|
|
11
|
-
- Non-functional goals
|
|
12
|
-
- Behavior invariants
|
|
13
|
-
|
|
14
|
-
## D. Deterministic Execution Flow
|
|
15
|
-
1. Capture behavior invariants.
|
|
16
|
-
2. Define refactor units.
|
|
17
|
-
3. Apply one unit at a time.
|
|
18
|
-
4. Verify invariants after each unit.
|
|
19
|
-
5. Measure complexity delta.
|
|
20
|
-
6. Emit refactor report.
|
|
21
|
-
|
|
22
|
-
## E. Structured Output Template
|
|
23
|
-
- `target`
|
|
24
|
-
- `invariants[]`
|
|
25
|
-
- `transformations[]`
|
|
26
|
-
- `behavior_check_results[]`
|
|
27
|
-
- `complexity_delta`
|
|
28
|
-
|
|
29
|
-
## F. Stop Conditions
|
|
30
|
-
- Invariant violation.
|
|
31
|
-
- Missing baseline behavior.
|
|
32
|
-
|
|
33
|
-
## G. Safety Constraints
|
|
34
|
-
- Abort on behavior-change risk.
|
|
@@ -1,34 +0,0 @@
|
|
|
1
|
-
# /scaffold
|
|
2
|
-
|
|
3
|
-
## A. Intent
|
|
4
|
-
Create deterministic project/module boilerplate with secure defaults.
|
|
5
|
-
|
|
6
|
-
## B. When to Use
|
|
7
|
-
Use to initialize new modules/features with approved structure.
|
|
8
|
-
|
|
9
|
-
## C. Required Inputs
|
|
10
|
-
- Target module name
|
|
11
|
-
- Runtime/stack
|
|
12
|
-
- Required patterns
|
|
13
|
-
|
|
14
|
-
## D. Deterministic Execution Flow
|
|
15
|
-
1. Validate target path non-conflict.
|
|
16
|
-
2. Resolve scaffold template.
|
|
17
|
-
3. Generate file tree.
|
|
18
|
-
4. Apply secure defaults.
|
|
19
|
-
5. Generate baseline tests.
|
|
20
|
-
6. Emit scaffold manifest.
|
|
21
|
-
|
|
22
|
-
## E. Structured Output Template
|
|
23
|
-
- `target`
|
|
24
|
-
- `template_source`
|
|
25
|
-
- `files_created[]`
|
|
26
|
-
- `secure_defaults[]`
|
|
27
|
-
- `tests_created[]`
|
|
28
|
-
|
|
29
|
-
## F. Stop Conditions
|
|
30
|
-
- Path collision.
|
|
31
|
-
- Unsupported template/runtime.
|
|
32
|
-
|
|
33
|
-
## G. Safety Constraints
|
|
34
|
-
- Do not overwrite existing files without explicit confirmation.
|