Loading...
Loading...
Found 10,694 Skills
Use when designing, critiquing, or implementing forms, inputs, validation, checkout, registration, payment, or any data-entry flow.
Generate, sign, and verify SBOMs and provenance attestations to secure the software supply chain. Use when implementing SLSA controls, artifact trust policies, or compliance evidence for releases.
Name a project to a naming convention you already use, then prove the name is free on the domain, npm, and GitHub before you commit to it. Use when the user says "name this project", "what should I call this", "give me project name ideas", "come up with a name for X", "is <name> taken", "check if this name is available", or "/namekit".
Integrates react-native-nitro-google-signin (Nitro Universal Google Sign-In) in React Native and Expo apps. Use when adding Google Sign-In, One Tap sign-in, GoogleOneTapSignIn, Credential Manager, SHA-1 OAuth setup, google-services.json, GoogleService-Info.plist, Expo config plugin, DEVELOPER_ERROR, or webClientId autoDetect.
OpenTelemetry semantic convention lookup and naming guidance. Use when selecting released semantic convention groups, attributes, or span naming rules, or when checking semantic convention compliance.
꿈 해몽 앱 첫 사용자 온보딩 5단계 패턴 (환영·기능 소개·맥락별 권한 요청·동의·첫 꿈 입력 안내). react-joyride·intro.js-react·shepherd.js·@reactour/tour·직접 구현 비교, 마이크/알림 *맥락 시점* 권한 요청, 학술 한계(의학·심리학 진단 아님 / 민속학적 자료) 사용자 친화 변환, 위기 자원 사전 안내, 페르소나 분기(일반·청소년·전문가), 스킵·재방문 UX, 접근성, 측정 지표, 흔한 함정을 다룬다. <example>사용자: "꿈 해몽 앱에 첫 사용자 온보딩을 어떤 라이브러리로 만들지?"</example> <example>사용자: "온보딩에 학술 한계 고지를 어떻게 부드럽게 넣을 수 있어?"</example> <example>사용자: "권한 요청을 온보딩 어디에 배치해야 거부율이 낮아져?"</example>
複数module・data ownership・system-wide trade-off・公開契約・target/transition architecture・migration/recoveryを、product valueと品質scenarioから設計するときに使う。局所class改善、流行architecture選定、単一契約抽出には使わない。
契約による設計で、自然言語要件を事前条件・事後条件・不変条件・失敗保証・冪等性・契約テスト仕様へ変換するときに使う。一般的なテスト追加、UI入力検証だけ、統合実装全体には使わない。
This skill is activated when the user's team faces execution problems—such as failing to meet OKRs, constantly changing plans, and passive team response to instructions. Typical trigger signals: Goals are set but execution deviates, plans can't keep up with changes, and the team only completes assigned tasks without proactive thinking. Non-trigger scenarios: Execution is good and only needs fine-tuning, the problem lies at the strategic level rather than the execution level, and individual work does not require a team execution framework. Difference from the "Strategy-Tactics Dialectics" skill: This skill solves "how to balance the three dimensions of execution" (execution layer), while the latter solves "dialectical design of offensive and defensive levels" (strategy layer).
Design to iOS and Android conventions — what each OS mandates, where they diverge, and when to unify. Use when shipping native apps. For breakpoint adaptation use `responsive-design`; for matching competitor patterns use `jakobs-law` (interaction-design).
국내 여행자의 조건을 먼저 묻고, 세 가지 여행 방향 중 사람이 고른 뒤 실제 정보를 확인해 휴대폰용 HTML 여행 보드를 만드는 스킬입니다.
Preserve code intent with selective comments and protect meaningful existing comments.