Recommend technology stacks for modern insurance agencies. TRIGGERS - Use when user needs help with insurance-tech-stack related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
22 件 ・ 関連度順
概要と使いどころ
Recommend technology stacks for modern insurance agencies. TRIGGERS - Use when user needs help with insurance-tech-stack related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Guide technology stack for accounting firms. TRIGGERS - Use when user needs help with accounting-tech-stack related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Guide technology stack for accounting firms. TRIGGERS - Use when user needs help with accounting-tech-stack related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Skill for tech-stack tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Health-check the user's Claude Code setup and fix issues: diagnose installation health — what the `claude doctor` terminal diagnostics cover — from local data (duplicate or leftover installs, PATH, unparseable settings files, broken or colliding agent definitions, skills whose frontmatter fails to parse); find unused skills, MCP servers, and plugins versus their context cost and disable dead weight; deduplicate local CLAUDE.md files against checked-in ones; trim checked-in CLAUDE.md files by cutting content a session could derive from the codebase (directory layouts, tech-stack lists, architecture overviews) while keeping gotchas, rationale, and non-standard conventions; migrate always-loaded CLAUDE.md guidance into lazy skills and nested CLAUDE.md files; flag slow hooks and context-heavy extensions; check the installed version is current; make auto mode the default permission mode; and pre-approve frequently denied read-only commands. Use when the user asks for a doctor run, checkup, audit, tune-up, or cleanup of their Claude Code setup or configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a `conductor/` directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when setting up a project, creating or updating product docs, managing a tech stack file, defining development workflows, tracking work units, onboarding to an existing codebase, or running project scaffolding.
日本語の概要は準備中です。原文の説明を表示しています。
Technology stack evaluation and comparison with TCO analysis, security assessment, and ecosystem health scoring. Use when comparing frameworks, evaluating technology stacks, calculating total cost of ownership, assessing migration paths, or analyzing ecosystem viability.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and workflow.md files.
日本語の概要は準備中です。原文の説明を表示しています。
Reverse-engineer a company's sales and marketing tech stack from public signals. Detects CRMs, cold email tools, people databases, ad pixels, email delivery services, and outbound sending domains via DNS records, website source inspection, Apify technology profiling, blacklist checks, and public spam complaint searches. Works on single companies or batches. Outputs a structured markdown report per company.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate and compare technology stacks with TCO analysis, security assessment, and ecosystem health scoring. Use when comparing frameworks, calculating total cost of ownership, assessing migration paths, or analyzing ecosystem viability.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive technology stack evaluation and comparison tool with TCO analysis, security assessment, and intelligent recommendations for engineering teams
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to choose between technologies, frameworks, or tools — or says "which framework should I use", "compare X vs Y", "should we migrate from X to Y", "what database should I use", "calculate TCO".
日本語の概要は準備中です。原文の説明を表示しています。
Identify the technology stack powering any website — frameworks, CMS, analytics, hosting, CDN, payment processors, and marketing tools. Useful for competitive intelligence, sales prospecting, and technology landscape research.
日本語の概要は準備中です。原文の説明を表示しています。
Recommend technology stacks based on project requirements, team expertise, and constraints. Use when selecting frameworks, languages, databases, and infrastructure for new projects.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user is deciding, reviewing, or second-guessing a software architecture or tech-stack choice — monolith vs microservices vs serverless vs event-driven, backend language, database type, caching, CQRS/event sourcing, polyglot, or a migration like Strangler Fig. Triggers on "should I use microservices", "which database", "tech stack for", "system design", or "architecture review". For how to deploy, operate, and scale that design (CI/CD, cloud, Kubernetes, IaC), use devops.
日本語の概要は準備中です。原文の説明を表示しています。
Generate standardized .agent-os directory structure with product documentation, mission, tech-stack, roadmap, and decision records. Enables AI-native workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-activates during requirements analysis to evaluate technical stack compatibility, recommend appropriate technologies, and assess performance implications.
日本語の概要は準備中です。原文の説明を表示しています。
Generate or update docs/project-context.md — the single source of truth for project conventions, tech stack, and anti-patterns. Loaded by all agents as a "constitution" to ensure consistent behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Single-pass tech-stack detection with an agents/evidence/analysis/ write-up; explicit request only. Deep multi-pass audit → universal-project-analysis. Raw primitives → project-analysis-core.
日本語の概要は準備中です。原文の説明を表示しています。
[Architecture] Use when you need to research, analyze, and compare tech stack options as a solution architect.
日本語の概要は準備中です。原文の説明を表示しています。
Per-surface tech stack decision tables and development tooling options. Use during /create-prd-stack to present constraint-filtered options to the user.
日本語の概要は準備中です。原文の説明を表示しています。
Utility — fill the surface stack map in tech-stack.md and provision skills using intelligent resolution. Called by pipeline commands when tech stack info changes.
日本語の概要は準備中です。原文の説明を表示しています。