생활·취미 스킬

Web browser game development principles. Framework selection, WebGPU, optimization, PWA.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

VR/AR development principles. Comfort, interaction, performance requirements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Multiplayer game development principles. Architecture, networking, synchronization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Mobile game development principles. Touch input, battery, performance, app stores.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

3D game development principles. Rendering, shaders, physics, cameras.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

PC and console game development principles. Engine selection, platform features, optimization strategies.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

2D game development principles. Sprites, tilemaps, physics, camera.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Game art principles. Visual style selection, asset pipeline, animation workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Game development orchestrator. Routes to platform-specific skills based on project needs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AI驱动的综合健康分析系统，整合多维度健康数据、识别异常模式、预测健康风险、提供个性化建议。支持智能问答和AI健康报告生成。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provides reverse engineering techniques for CTF challenges. Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works before exploiting or solving it, including binaries, APKs, WASM, firmware, custom VMs, bytecode, game clients, malwar

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Siber Vatan CTF playbook — flag formats, web/reverse/forensics/blockchain/OSINT/stego/crypto recipes, and pivot heuristics tailored to the Turkish CTF circuit.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Capture The Flag challenge solving — reverse engineering, steganography, forensics, crypto, web exploitation, binary exploitation, OSINT. Pattern recipes for fast triage and direct exploitation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Pixel art w/ era palettes (NES, Game Boy, PICO-8).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Tech health check: documentation, security, architecture, data analysis. Use when user requests project audit, tech debt review, or health check.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

安全地管理用户账号信息（CRUD）。支持存储密码、API Key、Cookies 等敏感信息，并支持 TOTP (MFA) 代码生成。**所有涉及凭证存储的操作必须优先使用此技能**，不可用于账号注册。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

プロジェクトの定期点検（健康診断）。「健康診断して」「ヘルスチェックして」「プロジェクトの状態を確認して」「最近ほったらかしだったので点検して」といった依頼で発動する。放置されると危険が積み上がる項目——Dependabotの更新PR、セキュリティアラート、CIの失敗、依存パッケージの脆弱性、古い作業ブランチ、未コミットの変更——をまとめて棚卸しし、優先度付きで報告する。エンジニアが常駐しないチームでは週1回の実行を推奨する運用にしており、担当者が何も覚えていなくても「健康診断して」の一言で点検が回ることを目的とする。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Busabase-backed App-in-Skill dashboard for a revenue-based-financing (RBF) fund or private-credit book of many small SME contracts. Use when the user invokes $kelly-portfolio-health or /kelly-portfolio-health, wants to check portfolio health, AUM, repayment progress, concentration risk, or a watchlist of contracts with declining revenue. Human actions (flag a contract for review, clear a flag, leave a note) write directly onto the contract's own Busabase record — this skill never moves money or changes contract terms. Generic and brand-free — not tied to any specific company or fund.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detect OAuth access token theft and misuse by analyzing sign-in logs for impossible travel, new device patterns, token replay from unusual IPs, and anomalous scope requests via Microsoft Graph and Okta APIs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Focused Signals scout for PostHog setup health. Reads the project's active health issues — the deterministic findings of PostHog's own health checks (no live events, outdated SDKs, missing reverse proxy, absent web vitals, ingestion warnings, failing data-warehouse models, and more) — and decides which are genuinely worth surfacing. Unlike a one-signal-per-issue push, it bundles kind-clusters into a single finding, weights by real blast radius (cross-referencing actual event volume and reach), and prioritizes issues an agent can resolve via the MCP. Emits only above the confidence bar; otherwise writes durable memory and closes out empty. Self-contained peer in the signals-scout-* fleet — no dependencies on other skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Focused Signals scout for PostHog projects using feature flags. Watches the flag roster and the `$feature_flag_called` evaluation stream for contradictions between a flag's configured state and its real traffic: evaluation cliffs on healthy flags, ghost flags (code calling keys that no longer exist), response-distribution shifts with no corresponding flag edit, and flag debt (stale, fully-rolled-out, or dead flags still burning evaluations). Emits findings only when they clear the confidence bar; otherwise writes durable memory and closes out empty. Self-contained peer in the signals-scout-* fleet — no dependencies on other skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnoses the health of a project's PostHog SDK integrations — which SDKs are out of date and how to fix them. Use when a user asks about PostHog SDK versions, outdated SDKs, upgrade recommendations, "SDK health", "SDK doctor" (the former name), or when events or features seem off and it might be due to an old SDK.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Daily per-section review cycle driving a section toward the smallest, clearest form that still does everything it does today. Selects its section live each run (scripted), inventories every file, derives the target shape before any scan, works parallel reading threads into one ranked list and strikes it on a 2-3h budget. One PR per run; each run's report and Needs-Peter queue live in its own docs/health/runs/ file, and a session-only purpose/surface/debt review is shown in the session; 'resume' applies Peter's answers later. Use for the morning section-improvement run, 'doctor <section>', or 'run section doctor'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.