Skill "tech-spec" from duc01226/EasyPlatform, covering quick summary, the generator contract (non-negotiable), c9 — the harvest detector reports; it never gates, step 0 — scope gate (mandatory first) and step 1 — derive the facts (grep, never recall).
★not rated 12▲
+1
changed 3d agoA41 tokens
originalMIT
Goal: Deliver a user-confirmed tech stack for every required layer, backed by researched alternatives, weighted evidence, and confidence, so the team chooses fit for scale, budget, skills, and timeline—not familiarity.
Goal: Hand the developer an evidence-backed wrap-up of the session — a Session summary first (Done · Key changes · Why · How it works), then the detail, doc/spec staleness flags and root-cause lessons — delivered as a self-contained HTML report opened for them, WITHOUT changing any repository file, so they understand…
Goal: Review UI code for WCAG 2.2 accessibility, Core Web Vitals performance, and modern web design best practices to identify evidenced issues and prioritize improvements.
★not rated 12▲
+1
changed 3d agoASkillSpector: warn25 tokens
originalMIT
Goal: Run broad web research, classify and deduplicate candidate sources, and produce a tiered source map + gap list for source-deep-dive, never a final report.
★not rated 12▲
+1
changed 3d agoASkillSpector: warn45 tokens
originalMIT
Read the registry → workflows.workflow-architecture-audit together with this skill. Call $start-workflow workflow-architecture-audit to resolve the selected mode, pre-actions and fingerprint.
Read the registry → workflows.workflow-big-feature together with this skill. Call $start-workflow workflow-big-feature to resolve the selected mode, pre-actions and fingerprint.
Read the registry → workflows.workflow-bugfix together with this skill. Call $start-workflow workflow-bugfix to resolve the selected mode, pre-actions and fingerprint.
Read the registry → workflows.workflow-code-to-spec together with this skill. Call $start-workflow workflow-code-to-spec to resolve the selected mode, pre-actions and fingerprint.
★not rated 12▲
+1
changed 3d agoASkillSpector: warn32 tokens
originalMIT
Read the registry → workflows.workflow-e2e together with this skill. Call $start-workflow workflow-e2e to resolve the selected mode, pre-actions and fingerprint.
Goal: Close the active workflow with evidence-backed coverage, spec-sync, graph, and baseline checks (reusing the run's own coverage and spec-sync evidence when it exists); deliver a diff-gated one-way comprehension recap unless $watzup follows and owns it, then retain per-session recovery state until explicit /clear…
Read the registry → workflows.workflow-feature-spec together with this skill. Call $start-workflow workflow-feature-spec to resolve the selected mode, pre-actions and fingerprint.
Read the registry → workflows.workflow-feature together with this skill. Call $start-workflow workflow-feature to resolve the selected mode, pre-actions and fingerprint.
Read the registry → workflows.workflow-greenfield-init together with this skill. Call $start-workflow workflow-greenfield-init to resolve the selected mode, pre-actions and fingerprint.
Read the registry → workflows.workflow-refactor together with this skill. Call $start-workflow workflow-refactor to resolve the selected mode, pre-actions and fingerprint.
Read the registry → workflows.workflow-research together with this skill. Call $start-workflow workflow-research to resolve the selected mode, pre-actions and fingerprint.
Read the registry → workflows.workflow-review-changes together with this skill. Call $start-workflow workflow-review-changes to resolve the selected mode, pre-actions and fingerprint.
★not rated 12▲
+1
changed 3d agoASkillSpector: warn56 tokens
originalMIT
Read the registry → workflows.workflow-seed-test-data together with this skill. Call $start-workflow workflow-seed-test-data to resolve the selected mode, pre-actions and fingerprint.
Read the registry → workflows.workflow-spec-sync together with this skill. Call $start-workflow workflow-spec-sync to resolve the selected mode, pre-actions and fingerprint.
Use when making system design decisions, reviewing architecture, or writing an ADR — covers cross-service, security, and performance impact of new or changed services.
★not rated 12▲
+1
changed 3d agoA32 tokens
originalMIT
Use when implementing backend-only work across APIs, services, libraries, data access, messaging, or jobs — following the project's actual architecture.
★not rated 12▲
+1
changed 3d agoB31 tokens
originalMIT
Use when reviewing code after a feature, before merging a PR, or when assessing quality and technical debt — produces a file-by-file plus holistic report.
★not rated 12▲
+1
changed 3d agoB34 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: