skills/magnus919_agent-skills
1
0
Fork 0
mirror of https://github.com/magnus919/agent-skills.git synced 2026-09-12 12:06:29 +03:00
Code Issues Packages Projects Releases Wiki Activity
809 Commits 11 Branches 10 Tags
dependabot/github_actions/actions/github-script-9
Commit Graph
5 Commits
Author SHA1 Message Date
Magnus HedemarkandGitHub 73a4250f74 feat: add software architecture methodology (#358) 
Add system-level architecture design, tradeoff, distributed workflow, evolution, facilitation, template, eval, and adjacent-owner routing guidance.\n\nAI-assisted: Jasper orchestrated implementation and verification with OpenCode.

Signed-off-by: Magnus Hedemark <magnus919@pm.me>
 2026-08-21 02:03:24 -04:00
Magnus HedemarkandGitHub db2ad850be feat(architecture): deepen codebase analysis (#355) 
Add evidence lenses for characteristics, coupling, decomposition, data authority, workflows, health reporting, and eval coverage.\n\nAI-assisted: Jasper orchestrated implementation and verification with OpenCode.

Signed-off-by: Magnus Hedemark <magnus919@pm.me>
 2026-08-21 00:09:03 -04:00
Magnus Hedemark a5f7e74972 fix: resolve skill audit findings 2026-07-11 09:24:58 -04:00
Magnus Hedemark 738ec715e7 Add human-focused README.md to every skill and bundle directory 
Each README is written for a human audience, explaining:
- What the skill does (not what format it follows)
- What benefit the user gets from installing it
- Quick setup and usage patterns
- When to load/trigger the skill
- What scripts, references, and templates it ships

data-scientist already had a README — left unchanged.

48 READMEs added across all skill and bundle directories.
 2026-07-09 22:30:12 -04:00
Magnus Hedemark 941d5c36dc feat: add software-architecture-analysis skill 
7-phase methodology for reverse-engineering codebases and producing
clean-room design documents under new constraints. Core workflow:

Phase 1: Clone & map repository structure
Phase 2: Find key architectural files (sort by line count)
Phase 3: Map architecture with Mermaid diagrams
Phase 3b: Extract implicit storage/provider contracts (DAO design)
Phase 4: Inventory feature surface
Phase 5: Write clean-room specification (no code contamination)
Phase 6: Break constraints (local-first, privacy-first redesign)
Phase 7: Post-delivery QA (link integrity, diagram rendering)

Includes a full worked example of the interface extraction pattern
(references/interface-extraction-pattern.md) using the cashew
thought-graph library — demonstrating all five steps from philosophy
reading through two-provider proof concept.

Signed-off-by: Jasper <magnus@groktop.us>
 2026-05-21 22:36:29 -04:00