compact-rules
Compact Rules (compact)
Cut: duplicate wording; long “why” where the rule is already clear; examples in separate sections — fold into the rule line.
Keep: every instruction; every distinct constraint.
How: Each rule self-contained. If it only makes sense with a detached example, rewrite so the example is inline (e.g. “Drop filler (just/really) — prefer ‘I think…’ over ‘I just really think…’”).
More from olamedia/analytics-skills
analyze-project
Use when starting work on any project to produce or update living documentation (TechStack.md, ProjectStructure.md) that bootstraps context for any AI agent session. Run before any feature work, or periodically to keep docs current.
13humanizer
>-
12architect
>-
12goal-definition
Use when you have a raw idea or request and need to define a clear goal with success criteria before exploring solutions. Use when requirements are vague, when "what does done look like" is unclear, or when assumptions need surfacing.
11prd
Use when you have a chosen direction and need to formalize requirements into a Product Requirements Document. Use when user stories, acceptance criteria, and scope boundaries need to be written down before architecture or implementation.
10analyze
Use when you have a raw idea or request and want to run the full analytics pipeline automatically — from research through to an interlinked task list. Best for straightforward problems where the full pipeline can flow with minimal back-and-forth.
10