个人作者

Yashpreet

更新于 2026-09-09

Skills
58
仓库
1
职业覆盖
0
场景覆盖
0
Stars
★ 0

Yashpreet 的 Skills 58

yashpreeto7
yashpreeto7/sanctum

web-design-guidelines

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

★ 0
yashpreeto7
yashpreeto7/sanctum

verification-loop

A comprehensive verification system for Claude Code sessions. Use when verifying a Claude Code session's work before claiming it is complete.

★ 0
yashpreeto7
yashpreeto7/sanctum

ui-ux-pro-max

UI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local data: 79 searchable styles (50 active), 192 product palettes and reasoning profiles, 74 font pairings, 119 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.

★ 0
yashpreeto7
yashpreeto7/sanctum

to-tickets

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

★ 0
yashpreeto7
yashpreeto7/sanctum

to-spec

Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

★ 0
yashpreeto7
yashpreeto7/sanctum

writing-skills

Use when creating new skills, editing existing skills, or verifying skills work before deployment

★ 0
yashpreeto7
yashpreeto7/sanctum

writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code

★ 0
yashpreeto7
yashpreeto7/sanctum

verification-before-completion

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

★ 0
yashpreeto7
yashpreeto7/sanctum

using-superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

★ 0
yashpreeto7
yashpreeto7/sanctum

using-git-worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

★ 0
yashpreeto7
yashpreeto7/sanctum

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

★ 0
yashpreeto7
yashpreeto7/sanctum

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

★ 0
yashpreeto7
yashpreeto7/sanctum

subagent-driven-development

Use when executing implementation plans with independent tasks in the current session

★ 0
yashpreeto7
yashpreeto7/sanctum

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

★ 0
yashpreeto7
yashpreeto7/sanctum

receiving-code-review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

★ 0
yashpreeto7
yashpreeto7/sanctum

finishing-a-development-branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

★ 0
yashpreeto7
yashpreeto7/sanctum

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

★ 0
yashpreeto7
yashpreeto7/sanctum

dispatching-parallel-agents

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

★ 0