8,135 件 ・ 関連度順
概要と使いどころ
Use for any code, documentation, config, dependency, test, review, or maintenance task in the Nauthilus repository that must follow AGENTS.md, POLICY.md, focused reproducer-first debugging, strict DRY/OOP boundaries, English comments, GOEXPERIMENT=runtimesecret test discipline, Makefile-driven validation, prompt-sync checks, and dirty-tree preservation.
日本語の概要は準備中です。原文の説明を表示しています。
Use for any code, documentation, config, dependency, test, review, or maintenance task in the Nauthilus repository that needs worktree hygiene, the project documentation map, focused reproducer-first debugging, Makefile-driven validation, and evidence-backed closeout.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting, stopping, or inspecting the dev stack for this Hydrolix Grafana datasource plugin — Grafana (with the plugin bind-mounted), ClickHouse, Keycloak (OAuth), and the on-demand playwright runner. Covers `docker compose up` semantics, the `dist/` prerequisite, serving plugin artifacts from an alternate folder (any path, live or frozen, via an ephemeral compose override), switching Grafana versions, hot-reload behaviour, delve attach, log streaming, OAuth/anonymous auth, and ClickHouse fixture access. Apply whenever a task needs the plugin running locally, needs to reset the stack, or needs to debug why Grafana won't come up.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building this Hydrolix Grafana datasource plugin — frontend webpack bundle (`dist/module.js*`) or Go backend binary (`dist/gpx_plugin_*`). Covers the split between host-built frontend and container-built Go, when each needs an explicit rebuild, watch vs one-shot, and the verification chain (typecheck / lint / unit tests). Apply for any task that edits `src/**`, `pkg/**`, `Magefile.go`, `webpack.config.ts`, or that needs to confirm `dist/` matches the working tree before running e2e or the dev stack.
日本語の概要は準備中です。原文の説明を表示しています。
Shape FriendlyBet product decisions, MVP scope, user stories, tournament flows, multi-sport expansion, pool mechanics, social competition loops, and feature prioritization. Use when planning what FriendlyBet should build, cut, sequence, or validate, especially for new sports, prediction formats, pool flows, leaderboards, sharing, or product strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Govern FriendlyBet agent values, professional standards, anti-hallucination behavior, truthfulness, risk reporting, AI resource discipline, feedback loops, skill improvement, performance reviews, decision-rights hygiene, and team quality. Use when creating, reviewing, promoting, correcting, or retiring agents; reducing hallucinations or mistakes; reviewing AI/tool usage; handling agent incidents; or aligning work with Eyal's philanthropic user-first approach.
日本語の概要は準備中です。原文の説明を表示しています。
Plan FriendlyBet ethical growth, SEO, README positioning, open-source contribution paths, self-hosting story, public trust, and discovery without ads, trackers, spam, or dark patterns. Use for repo-facing docs, growth strategy, launch positioning, SEO pages, contributor onboarding, or public messaging.
日本語の概要は準備中です。原文の説明を表示しています。
Model sports rules, event formats, prediction types, scoring implications, lock rules, data requirements, and provider constraints for FriendlyBet. Use when adding or comparing sports such as football, basketball, American football, tennis, tournaments, leagues, playoffs, brackets, weekly picks, or World Cup-specific logic.
日本語の概要は準備中です。原文の説明を表示しています。
Review or design FriendlyBet user experience, visual direction, mobile-first flows, premium sports interface, Hebrew/English copy fit, RTL behavior, accessibility, interaction patterns, and product UI polish. Use when a task touches screens, flows, layout, visual hierarchy, onboarding, prediction UX, share UX, or design quality.
日本語の概要は準備中です。原文の説明を表示しています。
Shape FriendlyBet Pundit content, bilingual product copy, community voice, share-card copy, social moments, video briefs, Hebrew/English wording, and group-chat friendly communication. Use when a task touches copy, Pundit tone, social videos, share text, community loops, or public-facing FriendlyBet voice.
日本語の概要は準備中です。原文の説明を表示しています。
Plan or review FriendlyBet architecture, implementation, schema, data flows, scoring, provider integrations, static/PWA behavior, Supabase/RLS impact, migrations, automation, and technical sequencing. Use when a task asks how to build, refactor, generalize, integrate, test, or safely ship FriendlyBet code.
日本語の概要は準備中です。原文の説明を表示しています。
Review FriendlyBet privacy, RLS security, auth, recovery codes, session storage, data minimization, public snapshots, share surfaces, legal/gambling wording, real-money risk, and compliance-sensitive product changes. Use when a task changes data access, user identity, public sharing, money-like language, security posture, or legal risk.
日本語の概要は準備中です。原文の説明を表示しています。
Create clear, comprehensive technical documentation for any audience
日本語の概要は準備中です。原文の説明を表示しています。
Document templates for all pipeline output documents — specs, indexes, reports, and strategy docs. Use when any workflow needs to produce a structured document.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic ambiguity resolution through tiered information gathering. Use when facing unclear requirements, unknown context, uncertain implementation choices, or any situation where guessing would be risky.
日本語の概要は準備中です。原文の説明を表示しています。
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
日本語の概要は準備中です。原文の説明を表示しています。
Use when about to claim work is complete, fixed, or passing — requires running verification commands and confirming output before making any success claims. Evidence before claims, always.
日本語の概要は準備中です。原文の説明を表示しています。
Design database schemas with normalization, relationships, and constraints. Use when creating new database schemas, designing tables, or planning data models for any database paradigm.
日本語の概要は準備中です。原文の説明を表示しています。
Use before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Manage database migrations and schema versioning. Use when planning migrations, version control, rollback strategies, or data transformations for any database paradigm.
日本語の概要は準備中です。原文の説明を表示しています。
Create Kotlin Compose design tokens from one of three supported sources — Google Stitch (MCP), Figma (MCP or JSON), or Claude Design (kta-design-spec output, Claude HTML/markdown artifacts). Three-layer architecture (Primitive/Semantic/Component) with code generation. Use when user asks to "generate design tokens", "create theme from Figma/Stitch/Claude design", "build Compose tokens from design spec", or "convert design source to tokens". Refuses any other input source and asks user for correct seed data.
日本語の概要は準備中です。原文の説明を表示しています。
Create Kotlin Compose design tokens from one of three supported sources — Google Stitch (MCP), Figma (MCP or JSON), or Codex Design (kta-design-spec output, Codex HTML/markdown artifacts). Three-layer architecture (Primitive/Semantic/Component) with code generation. Use when user asks to "generate design tokens", "create theme from Figma/Stitch/Codex design", "build Compose tokens from design spec", or "convert design source to tokens". Refuses any other input source and asks user for correct seed data.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when changing persisted local data, storage keys, caches, or any offline/sync behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when working on login, logout, session restore, tokens, route guards, or any authentication and authorization behavior.
日本語の概要は準備中です。原文の説明を表示しています。