49건 · 관련도순
AWS cost optimization, monitoring, and operational excellence expert. Use when analyzing AWS bills, estimating costs, setting up CloudWatch alarms, querying logs, auditing CloudTrail activity, or assessing security posture.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
DevOps and CI/CD expert. Use when setting up pipelines, containerizing applications, deploying to Kubernetes, or implementing release strategies. Covers GitHub Actions, Docker, K8s, Terraform, and GitOps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
6-pillar architecture review framework. Adapted from AWS Well-Architected for use by great_cto's architect agent on every non-nano ARCH document. Forces explicit answers across operational excellence, security, reliability, performance, cost, and sustainability — not just feature design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Excellence-first strategic decision support. This skill should be used when users need to choose between options, pressure-test a plan, evaluate risk, or make a specific decision — across security, product, growth, operations, org design, and finance. Use when there is a decision with tradeoffs to score and a recommendation to make. For pure research ("what does the best in the world do about X?"), use best-in-world-research instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert support operations guidance for customer service excellence. Use when designing ticket management systems, creating SLA policies, building support tier structures (L1/L2/L3), optimizing knowledge bases, defining severity levels and escalation procedures, implementing support metrics (CSAT, FRT, TTR, FCR), configuring support tool stacks, or building support-to-CS feedback loops. Covers Zendesk, Intercom, Freshdesk, and help desk best practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Marketing project management and execution excellence for B2B SaaS campaigns. Use this skill when coordinating multi-channel campaigns, allocating team resources, planning agile marketing sprints, running QBRs with clients, managing project timelines, balancing marketing workload, or implementing marketing operations scrum. Also triggers on: campaign coordination, resource allocation, agile marketing, sprint planning, client success, QBR, project timeline, marketing ops scrum, workload balancing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design operations and creative excellence for B2B SaaS marketing. Use this skill when building brand identity, designing landing pages, creating presentations, producing ad creative, or building infographics. Also triggers on: brand identity, landing page design, presentation, sales deck, ad creative, infographic, social media graphics, visual design, UI design, brand guidelines.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when configuring or operating the native Salesforce Data Export Service (Setup → Data Export) — weekly or monthly CSV export, attachment inclusion, file-size split, the 48-hour download window, and the gap between this free utility and the paid Salesforce Backup and Restore product. Triggers: 'data export service', 'weekly export', 'export attachments', 'data export 48 hour download', 'data export missing objects', 'is weekly export a backup', 'bulk api 2.0 query job export', 'data loader extract batch', 'process-conf.xml export', 'incremental export systemmodstamp', 'export inventory retention owner'. NOT for the paid Salesforce Backup and Restore product (use that as a separate tool), NOT for Bulk API extraction (use data/bulk-api-patterns), NOT for HA/DR architecture (use architect/ha-dr-architecture).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when authoring, reviewing, or maintaining Salesforce DevOps operational documents — runbooks, environment matrices, deployment guides, and post-deploy validation checklists. Triggers: 'runbook', 'environment matrix', 'deployment guide', 'pre-deploy checklist', 'post-deploy validation', 'how do I document a deployment', 'rollback procedure template'. NOT for what actually belongs on the pre-deploy gate — use devops/pre-deployment-checklist. NOT for release calendar, versioning, or go/no-go governance — use devops/release-management. Also covers: the devops-process YAML artefact (environment ladder, change-request state machine, deploy contract, deploy order, RACI), the deployOptions the runbook must record (checkOnly, testLevel, rollbackOnError, ignoreWarnings, purgeOnDelete, singlePackage, runTests), destructiveChangesPre/Post ordering, and the change-request emergency path.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when monitoring, diagnosing, or managing Batch Apex, Scheduled Apex, Queueable, and Flow scheduled jobs: Setup > Apex Jobs, AsyncApexJob queries, concurrent limits, failure detection, and notification patterns. NOT for writing the Batch or Schedulable class itself — use apex/batch-apex-patterns or apex/apex-scheduled-jobs. NOT for BatchApexErrorEvent alerting in code — use apex/scheduled-apex-failure-detection-and-monitoring. Trigger keywords: Setup > Scheduled Jobs, Apex Flex Queue, CronTrigger, CronJobDetail, FlowInterview, System.abortJob, System.schedule, CRON expression, Holding status, BLOCKED state, reschedule after sandbox refresh, scheduled job runbook.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, build, deploy, and operate production AI agent systems — single agents, multi-agent teams, and autonomous swarms. Complete methodology from agent architecture through orchestration, memory systems, safety guardrails, and operational excellence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
アプリのテストはすべてこのスキルを使う。開発中のTDD（テストファースト）から、 ユーザー目線のE2E・受入テスト、インフラ/デプロイ検証、リリース前の網羅テストまでを1つに統合。 「テストを書いて」「テストして」「動作確認して」「TDDで進めて」「カバレッジを確認」 「E2Eテスト」「リリース前にちゃんとテストしたい」「本番で動くか確認」「回帰テスト」 などの文脈で必ず使用する。§0「適用段階」に従い、たたき台〜v1 では「壊れたら困る順」の最小テスト、 固定化段階(v1 到達後のブラッシュアップ)ではユーザーがテストと明示しなくてもTDDサイクルを適用する。 セキュリティ・コスト・パフォーマンスの監査は Skill launch-security を併用する。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
アプリ・Webサービス・業務ツールの制作を、証拠分析→確定的な初稿→要件定義→体験設計→機能分解→実装→品質ゲート→リリース判定の手順ゲート制で進めるスキル。質問で要件を埋めるのではなく、依頼文・既存コード・資料・ログから最有力案を選び、動く成果物を先に出して差分で改善する。ユーザーが「アプリを作りたい」「ツールを作って」「〜を自動化したい」「システム化したい」「要件定義」「仕様を決めたい」「UI/UXを設計して」「体験を良くしたい」「機能を洗い出して」「MVPを決めたい」「品質チェック」「リリースしていいか判断して」などと言ったら必ず使用する。外部データの取込・マスタ・締め処理を伴う業務システムでは references/data-lifecycle.md も併用する。新規・既存を問わずアプリの制作・改善・リニューアルで使用する。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Marketing project management and execution excellence for B2B SaaS campaigns. Use this skill when coordinating multi-channel campaigns, allocating team resources, planning agile marketing sprints, running QBRs with clients, managing project timelines, balancing marketing workload, or implementing marketing operations scrum. Also triggers on: campaign coordination, resource allocation, agile marketing, sprint planning, client success, QBR, project timeline, marketing ops scrum, workload balancing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design operations and creative excellence for B2B SaaS marketing. Use this skill when building brand identity, designing landing pages, creating presentations, producing ad creative, or building infographics. Also triggers on: brand identity, landing page design, presentation, sales deck, ad creative, infographic, social media graphics, visual design, UI design, brand guidelines.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
建設的なフィードバックを提供し、早期にバグを発見し、チームの士気を維持しながら知識共有を促進する効果的なコードレビュー実践をマスター。プルリクエストのレビュー、レビュー基準の確立、開発者のメンタリング時に使用。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert database administrator specializing in high-availability systems, performance optimization, and disaster recovery. Masters PostgreSQL, MySQL, MongoDB, and Redis with focus on reliability, scalability, and operational excellence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert TypeScript engineering with advanced patterns, architectural design, performance optimization, testing strategies, and production-grade code quality. Use when building scalable TypeScript applications, implementing complex type systems, optimizing performance, designing maintainable architectures, or when the user asks for TypeScript engineering excellence, advanced patterns, or professional-grade code practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Be the COO with process design, organizational scaling, cross-functional execution, and operational excellence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.