6,784 件 ・ 関連度順
概要と使いどころ
Appwrite TypeScript SDK skill. Use when building browser-based JavaScript/TypeScript apps, React Native mobile apps, or server-side Node.js/Deno backends with Appwrite. Covers client-side auth (email, OAuth, anonymous), database queries, file uploads, real-time subscriptions, and server-side admin via API keys for user management, database administration, storage, and functions.
日本語の概要は準備中です。原文の説明を表示しています。
Parse and interpret execution debug logs generated by the EMULATORS framework, correlating each CPU instruction block with its VIC-II, CIA, SID, interrupt, stop, raster, badline, and memory-access cycles. Use for .LOG traces from EMULATORS when diagnosing cycle timing, raster effects, CPU stalls, IRQ/NMI entry, instruction/chip synchronization, or when reconstructing execution around a PC or mapped register.
日本語の概要は準備中です。原文の説明を表示しています。
Use when editing .vue files, creating Vue 3 components, writing composables, or testing Vue code - provides Composition API patterns, props/emits best practices, VueUse integration, and reactive destructuring guidance
日本語の概要は準備中です。原文の説明を表示しています。
Discipline for repairing a false claim once it has propagated: select what depends on it, produce a replacement, and accept with an expiring verdict. Trigger when: - A claim, citation, premise, or documented fact is found wrong and its downstream consequences must be traced and fixed. - A refutation, a failed re-run, a retracted external source, or a human correction lands against something already closed or already promoted. - Prompt contains: /remediation, remediation, retraction, false claim, propagated error, scrub, correction propagation, born-false, became-false, currency verdict, impeachment queue.
日本語の概要は準備中です。原文の説明を表示しています。
The case-law chronicle of this repo's major failures — symptom, root cause, evidence, status, and the rule each battle minted — so nobody re-fights a settled battle or re-proposes a rejected fix. Use when a bug/incident looks familiar ("didn't this happen before?"), when you're about to propose an approach that may have been tried and rejected (e.g. shipping a migration from a package), when someone asks "why does rule X exist" / "why is done-by-lgtm a thing" / "what was incident 988", or when a bug-archaeology run hits the shallow-clone wall and needs the pre-June-2026 history. Trigger phrases: "has this broken before", "why can't packages ship migrations", "why did graduation fail", "why is the green-build lesson a rule", "what did we learn from incident NN". (For a live "build is green but the app is broken" symptom, start at crouton-diagnostics-index. NB keep this description free of any space-then-hash sequence — an unquoted YAML scalar treats space-hash as a comment start and silently truncates.)
日本語の概要は準備中です。原文の説明を表示しています。
The migration step and the package-owned-table exception — NOT the normal collection flow. For app collections use the crouton CLI/skill (schema JSON → `crouton config`); reach here when you then need to generate/apply the Drizzle migration and hit the schema.mjs-only-after-build gotcha ("No schema files found"), or when adding a package-owned infra table (the crouton-flow pattern) that does NOT go through `crouton config`.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a proven POC into a real, crouton-native, documented package(s) + a consuming app — the deliberate "step back and rebuild" checkpoint. SPEC-DRIVEN — the POC discovers a behaviour spec (captured at each sign-off), graduation freezes it as authoritative, the app is rebuilt the crouton way to satisfy it, and nothing is done until it's checked + signed off against two gates (experience + crouton-conformance). Use when a `pocs/*` app is proven and "done", or asked to "graduate this poc", "make it a real app", "extract the package".
日本語の概要は準備中です。原文の説明を表示しています。
Analyze code changes and update relevant documentation to stay in sync. Runs automatically before /commit. Assumes docs are outdated — only updates what this change touches, never over-reaches.
日本語の概要は準備中です。原文の説明を表示しています。
Act on the queued items. Works through every pending item on the working todo list (the queue built with /list), actually doing each one, marking it in_progress then completed as you go. Use after stacking items with /list.
日本語の概要は準備中です。原文の説明を表示しています。
Process the batch of incoming Bridge Classroom feedback. Pull open `classroom-feedback` issues from the PBS repo, cluster them by defect class, verify each against the actual board, and fix at the right altitude — patch a single board, or (when a class recurs) build a gate, sweep the whole corpus, and regenerate/drop collectively. Engine bugs route to the Classroom repo; bridge-judgment calls go to Rick. Nothing leaves the machine without David's OK. Invoke as `/issue` (optionally with an issue number or scenario to restrict the run).
日本語の概要は準備中です。原文の説明を表示しています。
Test or debug application use cases through their public Action API, including persistence, authorization failures, atomic rollback, and post-commit reactions. Use when adding regression tests for business operations.
日本語の概要は準備中です。原文の説明を表示しています。
Create, modify, or debug business events and their follow-up reactions, including order cancellation events, queued listeners, transaction timing, and rollback behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a learner's technical level is unknown or uncertain, requiring diagnostic calibration before teaching begins.
日本語の概要は準備中です。原文の説明を表示しています。
Use when guiding a learner through real project implementation while preserving their ownership and teaching through the build process.
日本語の概要は準備中です。原文の説明を表示しています。
Use when capturing or restoring a learner's persistent profile to personalize teaching across sessions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the learner benefits from guided questioning to build reasoning and uncover misconceptions before receiving direct answers.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a learner has surface understanding and needs to explore mechanism, tradeoffs, edge cases, and production implications at depth.
日本語の概要は準備中です。原文の説明を表示しています。
Use when coaching hypothesis-driven debugging that requires the learner to gather evidence and reason about root causes before applying fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a learner asks to learn from a repository and the agent must map curriculum structure and prerequisites before teaching.
日本語の概要は準備中です。原文の説明を表示しています。
Solves complex, open-ended problems using a knockout tournament mechanism. Generates an initial population of diverse candidate answers, pairs them into head-to-head matches, produces a hybrid "child" solution from each pair, and advances the best of the three through a bracket until a winner emerges. Use this skill whenever the user wants to competitively select the best answer from a field of alternatives, asks for a "tournament" or "bracket" style search, wants a faster alternative to full evolutionary search, or uses phrases like: "run a tournament on this", "bracket-style search", "let solutions compete", "knockout search", "find the best answer by elimination", or "which solution wins?". Also trigger when the problem is open-ended and the user wants a clear winner quickly rather than a deep multi-generation refinement.
日本語の概要は準備中です。原文の説明を表示しています。
Continuous environmental scanning across six PESTEL categories — Political, Economic, Social, Technological, Environmental, Legal. Not a one-time analysis but an ongoing radar. Three modes. Diagnostic mode runs a full scan and prioritises forces by impact, speed, and reversibility. Review mode checks the watch list monthly for movement and new signals. Alert mode defines concrete monitoring triggers for each top force. Use whenever someone wants to understand external forces acting on their business, assess macro risk, prepare for planning, or check whether the world has moved since last time they looked. Connects to the strategy map (forces act on the chain) and Wardley Map (forces drive component evolution). Based on practice by Eterdis (eterdis.com).
日本語の概要は準備中です。原文の説明を表示しています。
Wardley Mapping for strategic positioning — map your value chain from customer need to underlying components, plot where each component sits on the evolution curve (novel to commodity), and spot the strategic plays that movement creates. Use this skill when someone wants to understand where their industry is heading, whether they're building things they should be buying, where competitors are vulnerable, what's about to become commoditised, or why their competitive advantage is eroding. Triggers on questions about build-vs-buy, component evolution, value chain analysis, commoditisation risk, or strategic positioning relative to market movement. Three modes — full diagnostic (build a map from scratch), review (update positions and reassess), and alert triggers (set tripwires for when components move). Based on practice by Eterdis (eterdis.com).
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing web UI in React, Next.js, Tailwind, CSS, or GSAP against an approved design, fast-path brief, or prototype UX contract.
日本語の概要は準備中です。原文の説明を表示しています。
Teach software development through active project work while still producing a working result, maintaining bilingual English and Chinese project documentation, protecting private context, and publishing reviewed updates to GitHub only after confirmation. Use when Codex helps the user create, build, extend, debug, refactor, document, publish, or understand a software project and the user's goal includes learning, mentorship, guided implementation, pair programming, understanding the code, or becoming able to do similar work independently.
日本語の概要は準備中です。原文の説明を表示しています。