docs: add architecture documentation for commands vs skills

[Shrinet82]

Summary

Addresses #5 by clarifying the distinction between commands and skills for community contributors.

Changes

• docs/ARCHITECTURE.md - Plugin structure overview explaining how plugins are loaded and how components interact
• docs/COMMANDS_VS_SKILLS.md - Detailed comparison explaining:
  • Commands = explicit actions triggered via slash commands
  • Skills = domain knowledge Claude retrieves automatically
  • Why overlap is intentional (commands define what, skills define how)
  • Practical guidelines for contributors
• README.md - Added links to new documentation

Motivation

Issue #5 correctly identified confusion about the relationship between commands and skills, particularly noting overlap between files like legal/skills/contract-review and legal/commands/review-contract. This documentation explains that the overlap is intentional and clarifies the distinct purposes.

Closes #5

[Shrinet82]

hi @mattpic-ant
I've submitted PR #14 which addresses Issue #5 regarding the confusion between commands and skills.

I've added a new docs/ directory containing:

Architecture Overview: Explaining how plugins are loaded and structured.
Commands vs Skills: A detailed guide clarifying the distinction and intended usage (addressing the specific points in the issue).
I would appreciate your review when you have a moment! Thanks.

[aromal-a]

PR: RAISED: ERROR IN RUNNER PICKUPS. Simple section of UI elements can force an immediate work-flow trigger. Keep cater to the already missing and unfinished. Check viability through cross-checking. Keep tracker of error encountered and give a raise to any PR that matches or . Put idol desolation in isolated,cointainered snippets.