74 件 ・ 関連度順
概要と使いどころ
Create a research thesis — theses/{nnn}-{slug}/ via mkdir-as-CAS, pillar-prioritized spec.md, initialized thesis.md, and the thesis-quality checklist. Refuses creation while the workspace constitution is unratified (spec 046 Q83 A+).
日本語の概要は準備中です。原文の説明を表示しています。
Institutional-grade equity research skills for AI agents. 80 Claude-type skills across 14 verticals (equity-research-core, models-and-pitches, bio-pharm, scenarios, quantitative-analysis, idea-generation, options-derivatives, business-intelligence, industry-analysis, macro-strategy, portfolio-strategy, technical-analysis, risk-and-psychology, trading-as-business) powered by agentii.ai's agent-use-ready SEC filing data plane — SEC filings and 15K+ earnings call transcripts, 15.99M XBRL facts, and company profiles for 1,146+ US-public-equity tickers. Features the three-layer retrieval protocol (Document Discovery → Page Map → Deep Read, with deep-outline escalation) — measured, not asserted: 97.5% saved against a sequential read, and the page map itself is 10.0% of one (spec 062 T030, 2026-09-23) — server-side parallel multi-period search via search_cross_period, a full Excel/PPT generation pipeline with 3-tier office backend support, and the spec-046 governance layer (constitution, thesis and single-skill modes, mechanical gates, and a template-owned disclaimer on generated reports).
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Crystal Growth Specialist. Use when a task calls for Crystal Growth Specialist judgment. Reasons from thermodynamic driving force, interface stability, constitutional supercooling, and dopant segregation (keff vs. k0, G/R) through Cz/Bridgman/FZ/LEC/PVT growth, CGSim and phase-field simulation, XRT topography, etch-pit counting, and FTIR/SIMS mapping while treating striations, inclusions, crucible-reaction contamination, and cool-down slip and cracking as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Expert guide for AI Safety, Governance, and Responsible AI in production — Constitutional AI enforcement, runtime guardrails (NeMo Guardrails 2.0, Llama Guard 3), bias auditing, hallucination detection, EU AI Act compliance, model cards, and content provenance / Panduan ahli untuk Keamanan AI, Tata Kelola, dan AI Bertanggung Jawab di produksi.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
日本語の概要は準備中です。原文の説明を表示しています。
用户需要为不同的人/场景定制方案时; 当"一刀切"方案失效时; 当需要根据个体差异(体质/能力/偏好)调整参数时。 不适用于: 标准化流程不需要定制的场景、群体层面的统一方案。
日本語の概要は準備中です。原文の説明を表示しています。
Conduct temperament-based health assessment from Hildegard von Bingen's Causae et Curae. Evaluates the four temperaments (sanguine, choleric, melancholic, phlegmatic), elemental correspondences (air, fire, earth, water), and provides dietary and lifestyle recommendations for rebalancing. Use when understanding constitutional type in Hildegardian terms, experiencing imbalance (fatigue, digestive issues, mental fog) needing holistic guidance, seeking dietary recommendations by temperament, or researching medieval humoral medicine.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
日本語の概要は準備中です。原文の説明を表示しています。
"SME and family-business management for Taiwan's industrial structure (98% SME, 70%+ family-controlled listed). Integrates four pillars: resource-constrained decision-making, family governance (Tagiuri-Davis three circles), four-layer succession, and professionalization. Use for sub-200-employee strategy, capital-constrained prioritization, family-vs-professional-manager conflict, founder handover, family-constitution design, or SME financing limits. Triggers: 『二代接班』『家族企業』『中小企業』『家族憲章』『家族辦公室』『傳承規劃』『小公司策略』『資源有限』『家族跟專業經理人』『三圓模型』『隱形冠軍』. For 成大 EMBA SME strategy, 政大 EMBA family-business succession, 逢甲 EMBA SME management cases. Fills Asgard gaps in resource-constrained strategy and Chinese-family governance.".
日本語の概要は準備中です。原文の説明を表示しています。
Transforms police body camera transcripts into structured 10-section legal summaries with timestamp-cited verbatim statements, constitutional issue spotting, evidence inventory, and probable cause articulation. Maintains strict neutrality for all parties. Use when analyzing BWC footage for discovery, pre-trial prep, or trial. Trigger: body camera, BWC, body worn camera, officer footage, use of force review, incident summary.
日本語の概要は準備中です。原文の説明を表示しています。
Generate or update docs/project-context.md — the source of truth for conventions, tech stack, and anti-patterns, loaded by all agents as a constitution.
日本語の概要は準備中です。原文の説明を表示しています。
Run an org-team workflow — a flat pod of up to four peer Claude Code sessions claims lane-tagged slices of an approved spec over the baseline MCP channel and implements them concurrently, each in its own git worktree. Each peer DECIDES its own in-lane implementation choices in its own main context (Article X); only un-decidable or cross-lane forks escalate peer→lead→human (yield_fork for task-bound forks, ask_lead for free-form queries). Opt-in and OFF by default (velocity.org_mode.enabled). Graduates the retired sprint-dispatch prototype into the constitutionally-sanctioned org-team model (Article X — Multi-session coordinated workflows). Requires git.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a non-destructive post-implementation verification gate validating the implementation against spec.md, plan.md, tasks.md, and constitution.md.
日本語の概要は準備中です。原文の説明を表示しています。
Multiple agents draft a structured document through federated co-authorship and formal voting.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update project governing principles and development guidelines. Use at project start to establish code quality, testing standards, and architectural constraints that guide all development.
日本語の概要は準備中です。原文の説明を表示しています。
Break a user interface under real-world conditions across responsiveness, hostile content, interaction states, accessibility, network failure, interruption, and complete user journeys, reporting observable user harm with evidence rather than aesthetic opinion. Use whenever the user wants to stress-test a UI, verify responsive and edge-case behaviour, inspect loading/error/empty/recovery states, review a flow for friction, or find where an interface fails under reality. Part of the audit suite; inherits the shared constitution while its own job is proving observable user harm.
日本語の概要は準備中です。原文の説明を表示しています。
Control risky structural change by proving a refactor is necessary and that behaviour, contracts, data, security boundaries, and operational properties can be preserved through a staged migration. Use whenever the user wants to refactor, restructure, clean up, modernise, extract, migrate, rewrite, or re-architect existing code, or asks whether they should. Prefer this over starting the refactor. DO NOT REFACTOR is a first-class outcome. Part of the audit suite; inherits the shared constitution while its own job is proving necessity and behavioural preservation.
日本語の概要は準備中です。原文の説明を表示しています。
Design a test strategy around product risk, business invariants, failure modes, and existing controls, deciding what deserves testing and at which boundary rather than maximising coverage. Use whenever the user asks how to test something, wants a test plan or strategy, is deciding between unit/integration/contract/E2E/property/concurrency testing, or wants to know whether existing tests actually protect what matters. Prefer this over writing tests immediately. Part of the audit suite; inherits the shared constitution while its own job is proving risk coverage.
日本語の概要は準備中です。原文の説明を表示しています。
Reproduce, isolate, and diagnose a specific software failure before changing production behaviour, then propose the smallest safe fix with regression protection. Use whenever the user reports a bug, crash, error, stack trace, flaky test, incorrect output, "works on my machine," intermittent failure, regression after a deploy, or any behaviour that diverges from expectation and the cause is not obvious. Prefer this over jumping straight to a fix. Part of the audit suite; inherits the shared constitution, while its own job is proving causality.
日本語の概要は準備中です。原文の説明を表示しています。
Map and attack the authentication, authorization, session, tenant, federation, and machine-identity boundaries of a system, proving whether access controls actually hold rather than whether they appear to. Use whenever work touches login, sessions, tokens, roles, permissions, multi-tenancy, password reset, invitations, OAuth/OIDC/SAML, API keys, service accounts, webhooks, admin impersonation, or any question of "can this actor do or see this thing." Prefer this over a generic security pass for identity-heavy surfaces. Part of the audit suite; inherits the shared constitution while its own job is proving or disproving access boundaries.
日本語の概要は準備中です。原文の説明を表示しています。
You are an expert prompt engineer specializing in crafting effective prompts for LLMs through advanced techniques including constitutional AI, chain-of-thought reasoning, and model-specific optimizati
日本語の概要は準備中です。原文の説明を表示しています。
design step of mspec workflow — write design.md + design-rationale.md + architecture-overview.md, full Constitution Check
日本語の概要は準備中です。原文の説明を表示しています。
Hard readiness gate before implementation begins — cross-checks the constitution, feature spec, plan, and tasks for consistency, traceability, and unresolved ambiguity. Returns PASS or FAIL with specific findings. Load when the spec-driven-development orchestrator routes /analyze, when the user asks to cross-check spec vs plan, audit traceability, verify spec readiness, gate-check before implementation, or says "is this spec implementation-ready", "trace requirements to tasks", "/analyze", "spec sanity check", "spec readiness gate", "spec consistency check". Output: docs/reviews/YYYY-MM-DD-<slug>-spec-crosscheck.md.
日本語の概要は準備中です。原文の説明を表示しています。
Tactical fast path: turn a small problem, bug report, edit request, or narrow refactor into three deliverables — a brief change-spec (docs/specs/), a detailed implementation-ready plan (docs/plans/), and a TODO.md with agent-pickable tasks and milestones. Load when the user describes a tactical problem and wants quick planning artifacts, says "plan this change", "create a TODO", "write a plan for this", "problem to plan", "break this into tasks for agents", "I want to change X — plan it", or when process-decomposer routes here after determining the user needs lightweight planning deliverables. Also triggers on "create tasks from this problem", "make this actionable", or "turn this into a plan agents can execute". For feature-sized work that needs an executable spec + constitution + cross-check gate, route to `spec-driven-development` (or `feature-spec`) instead.
日本語の概要は準備中です。原文の説明を表示しています。