304 件 ・ 関連度順
概要と使いどころ
Add or revise source-level Rustdoc for Shift Rust APIs. Use before writing or editing documentation comments in `.rs` files, especially for public or crate-visible APIs, domain structures, compiler adapters, persistence boundaries, trait implementations, unsafe code, or any API where ownership, units, coordinate spaces, mutation, I/O, sparse behavior, failure modes, panics, or concurrency are easy to misunderstand.
日本語の概要は準備中です。原文の説明を表示しています。
Convert between construction measurement units. Handle metric/imperial conversion, area/volume calculations, and unit normalization for CWICR data.
日本語の概要は準備中です。原文の説明を表示しています。
Pulls financial statement numbers for US public companies straight from SEC EDGAR's free official XBRL APIs (companyfacts, companyconcept, frames, submissions) into a cited table. Every value carries its accession number, form, fiscal period, filed date, XBRL tag and a link to the filing, and the tool handles fiscal-year ends, quarterly vs YTD vs TTM, derived Q4, restatements and units. Use this whenever the user wants 10-K numbers or 10-Q numbers, says "pull financials for", asks for public company revenue, net income, EPS, cash, debt or capex, wants comps or a competitor side-by-side, a credit check, prospect research, or model inputs, or mentions SEC filings or EDGAR, even if they never say XBRL. Free and primary-source, no paid data terminal needed. Do not use it for private companies, stock prices or valuation multiples.
日本語の概要は準備中です。原文の説明を表示しています。
Use Astropy core for astronomy units, coordinates, times, tables, FITS/WCS files, modeling, statistics, visualization, cosmology, configuration, and public CLIs.
日本語の概要は準備中です。原文の説明を表示しています。
Same pixels, fewer tokens — for user-facing deliverables where visual polish is the spec. Use when building or editing a landing page, marketing site, hero, pricing/feature section, dashboard, or any HTML/CSS UI component. Keeps the full rendered design (layout depth, hierarchy, motion, responsive richness, a11y) and cuts tokens by expressing that design densely — CSS custom properties, shared classes, shorthand, fluid units — instead of by cutting the design. The honey core trims code and prose; this trims how the design is *written*, never how it looks. Reach for it whenever output is user-facing markup, even if the user never says "minimal".
日本語の概要は準備中です。原文の説明を表示しています。
Same pixels, fewer tokens. For user-facing markup: keeps the full design, expresses it densely with CSS vars, shorthand, fluid units.
日本語の概要は準備中です。原文の説明を表示しています。
Break a trusted implementation plan (or other provided context) into independently-grabbable, atomic work items, written to a single work-items.md file. Use when the user wants to convert a plan into work items, create implementation tickets or tasks, divide a plan into work units, or break the plan down into grabbable pieces. Do not use when there is no implementation plan yet or the plan is not yet trusted — use plan-implementation to produce the plan or iterative-plan-review to harden it first. Does not sequence work into demoable delivery phases — use plan-a-phased-build for that. Does not write code — use tdd to implement a work item.
日本語の概要は準備中です。原文の説明を表示しています。
Break down full NeurIPS reviewer responses into structured rebuttal units. Use when input contains NeurIPS reviewer fields (Summary, Strengths and Weaknesses, Questions, Limitations) and numeric scores (Rating, Confidence, Quality, Clarity, Significance, Originality). Splits questions and limitations into granular response items while preserving original wording for quoted issues.
日本語の概要は準備中です。原文の説明を表示しています。
Break down full ARR (ACL Rolling Review) reviewer responses into structured rebuttal units. Use when input contains ARR reviewer fields (Paper Summary, Strengths, Weaknesses, Comments/Suggestions) and numeric scores (Confidence, Soundness, Excitement, Overall Assessment, Reproducibility). Splits weaknesses and comments/suggestions into granular response items while preserving original wording for quoted issues.
日本語の概要は準備中です。原文の説明を表示しています。
Break down full ICLR reviewer responses into structured rebuttal units. Use when input contains reviewer summary/presentation/contribution/strength/weakness/question text and the goal is to split weaknesses/questions into granular R-style response items while preserving original wording for quoted issues.
日本語の概要は準備中です。原文の説明を表示しています。
Break down full ICML reviewer responses into structured rebuttal units. Use when input contains reviewer summary/presentation/contribution/strength/weakness/question text and the goal is to split weaknesses/questions into granular R-style response items while preserving original wording for quoted issues.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Algebraist. Use when a task calls for Algebraist judgment. Reasons from carriers, operations, and morphisms through isomorphism theorems, universal properties, exact-sequence and homological tools (Ext, Tor, snake lemma), and computational systems like GAP, Magma, SageMath, and Lean while treating silently smuggled hypotheses (commutativity, units, Noetherian, algebraically closed base), characteristic-p false friends, and noncanonical isomorphisms as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Apply clean code principles when generating or modifying implementation code. Enforces function focus, naming clarity, complexity management, error handling, and self-documenting style. Use when the user mentions 'clean code', 'code quality', 'coding guidelines', or 'implementation quality'. Loaded automatically by the code-generating molecules (code-forge, refactor-safely, bug-fix). This skill governs the craft of writing individual code units -- not architecture (see architecture), not security posture (see secure-coding), not test structure (see test-quality), and not refactoring workflows (see refactor-safely).
日本語の概要は準備中です。原文の説明を表示しています。
Plain language applied to source code (ISO 24495-1:2023 principles). Governs the parts of code a person reads: the order units appear in, their names, comments, and error messages. Applied when writing or restructuring code, not when explaining it.
日本語の概要は準備中です。原文の説明を表示しています。
OPTIONAL per-task isolation for autonomous parallel work. Routed to only on explicit opt-in by subagent-driven-development or dispatching-parallel-agents, so parallel units mutate files without colliding. Stands up one worktree per unit, works it in isolation, then integrates each unit back onto the caller's working branch for the caller's single commit-gate + finishing-a-development-branch exit. Never on the default path; it does not bypass a gate or finish per unit.
日本語の概要は準備中です。原文の説明を表示しています。
Design multi-device layouts with Container Queries, clamp() fluid typography, :has() selector, subgrid, and modern CSS units (dvh/svh/lvh). Use when user asks to make a layout responsive, handle mobile/tablet/desktop breakpoints, create fluid typography, or use Container Queries. Do NOT use for full-page layouts (use landing-craft), component design (use component-forge), or animation-specific responsive (use motion-craft).
日本語の概要は準備中です。原文の説明を表示しています。
Use when building a 2D web game with Phaser (3.x/4.x) or PixiJS 8 in TypeScript - framework vs renderer, Phaser scenes/game objects/arcade physics/groups as pools/scale manager/loader, scene shutdown cleanup, PixiJS 8 async init, Assets bundles, ticker units and destroy, and keeping rules in plain TS modules.
日本語の概要は準備中です。原文の説明を表示しています。
Design a spaced retrieval schedule for any topic list and timeline. Use when planning units, term sequences, or revision programmes.
日本語の概要は準備中です。原文の説明を表示しています。
Design a project-based learning brief with a driving question, milestones, and assessment criteria. Use when planning PBL units, inquiry projects, or extended investigations.
日本語の概要は準備中です。原文の説明を表示しています。
Anchor a multidisciplinary unit in a real-world phenomenon that requires multiple subject lenses to understand. Use when designing integrated or phenomenon-based units across disciplines.
日本語の概要は準備中です。原文の説明を表示しています。
Design a service-learning project connecting genuine community need with embedded curriculum learning. Use when planning community projects, civic engagement, or social action units.
日本語の概要は準備中です。原文の説明を表示しています。
Design a structured goal-setting protocol using SMART or implementation-intention frameworks for students. Use when launching units, projects, or developing student self-direction habits.
日本語の概要は準備中です。原文の説明を表示しています。
Redesign a blocked topic sequence into an interleaved plan with mixed practice across related topics. Use when planning units, homework schedules, or revision programmes.
日本語の概要は準備中です。原文の説明を表示しています。
Classify curriculum content into Know, Understand, and Do categories to align teaching and assessment approaches. Use when planning units, writing objectives, or selecting assessment methods.
日本語の概要は準備中です。原文の説明を表示しています。