Pcms-React 에 사용된 frontend 기술스택에 대해 code와 설명을 곁들인 markdown문서를 생성한다.
สร้างแผนการสอน + แบบฝึกหัด/quiz + rubric การประเมิน + ไอเดียการบ้าน สำหรับครูไทยทุกระดับชั้น
Tealium integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tealium data.
Launches an agent team with a task file. Usage: /team [task-file2 ...] [--lang en] Example: /team TASK_SDD.md Example: /team TASK_REVIEW01.md TASK_REVIEW02.md
Shared team memory for Claude Code. Record lessons, decisions, and conventions that persist across sessions and team members.
Generate onboarding context for new team members from team brain knowledge. Use when user says 'onboard', 'onboarding', 'new developer', 'getting started', or '/team-brain…
Regenerate BRAIN.md and optionally generate .cursorrules and AGENTS.md from team brain entries. Use when user says 'sync', 'regenerate', 'update brain', or '/team-brain sync'.
中文优先：用于团队构建相关任务，帮助识别、设计、实现或验证对应工作流。English keywords: Interactive agent picker for composing and dispatching parallel teams
Reference skill for Zoom Team Chat. Use after routing to a chat workflow when building user-scoped messaging integrations, chatbot experiences, rich cards, buttons, slash…
You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows.
You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination…
Design optimal team structures, hiring plans, compensation strategies, and equity allocation for early-stage startups from pre-seed through Series A.
Unit Circle Laboratory + sc-dev-team autonomous mission control. Provides human-in-the-loop automation layer, pipeline management, context lifecycle, stuck-state prevention.
Free-form multi-agent delegation. Auto-builds team with DAG, parallelizes codex/gemini via background Bash.
Lightweight session execution skill. Resumes existing team-coordinate sessions for pure execution via team-worker agents.
Detects interpersonal friction, team tension, communication breakdown, and morale signals buried in internal email threads.
Multi-phase implementation: @claude-architect → Codex parallel + @claude-worker → Gemini parallel → @claude-finalizer.
OKR tracker page — quarter banner, three objectives with their key results as progress bars, owner avatars, status pills, and a "this quarter at a glance" sidebar.
Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days.
Unified team skill for performance optimization. Coordinator orchestrates pipeline, workers are team-worker agents. Supports single/fan-out/independent parallel modes.
Analyze task requirements and identify talent gaps. Compares needed expertise against available resources to determine if assembly and training phases are required.
Unified team skill for plan-and-execute pipeline. Pure router — coordinator always. Beat model is coordinator-only in monitor.md. Triggers on "team planex".
Unified team skill for code review. 3-role pipeline: scanner, reviewer, fixer. Triggers on team-review.
Centralized team management SDK for Rune workflows. Provides ExecutionEngine interface (TeamEngine), shared lifecycle protocols (teamTransition, cleanup, session isolation),…
Assess team structure against Skelton's Team Topologies. Evaluate cognitive load, interaction modes, and Conway's Law alignment.
Deep collaborative analysis team skill. Multi-role investigation with coordinator-driven synthesis. Triggers on "team ultra-analyze", "team analyze".
Team Up integration. Manage Organizations. Use when the user wants to interact with Team Up data.
Post project updates to team chat, gather feedback, triage responses, and plan next steps. Adapts to available tools (chat, git, issues, tasks).
Aggregate weekly team member updates from local .md/.txt files into a people-centric status report for managers.
Suivi de la vélocité d'équipe et des métriques agile pour piloter la performance et la prévisibilité.
Verify teammate code delivery. Checks completeness against task brief (feature.json) or backlog TODO, generates tests inline, maps results to requirements.
Teamcamp integration. Manage Organizations. Use when the user wants to interact with Teamcamp data.
Automate Teamcamp tasks via Rube MCP (Composio). Always search tools first for current schemas.
TeamCity integration. Manage data, records, and automate workflows. Use when the user wants to interact with TeamCity data.
Use when working with TeamCity CI/CD or when a user provides a TeamCity build URL — drives the `teamcity` CLI for builds, logs, jobs, queues, agents, pools, projects, and…
Teamdeck integration. Manage Organizations. Use when the user wants to interact with Teamdeck data.
TeamGantt integration. Manage data, records, and automate workflows. Use when the user wants to interact with TeamGantt data.
Teamgate integration. Manage data, records, and automate workflows. Use when the user wants to interact with Teamgate data.
Teamioo integration. Manage Organizations. Use when the user wants to interact with Teamioo data.
Teamleader integration. Manage Deals, Persons, Organizations, Leads, Projects, Pipelines and more. Use when the user wants to interact with Teamleader data.
DAG analysis for team tasks: validate, visualize, find ready tasks, critical path. Requires agent-teams CLI.
Teams Webhook Sender - Auto-activating skill for Business Automation. Triggers on: teams webhook sender, teams webhook sender Part of the Business Automation skill category.
TeamSupport integration. Manage data, records, and automate workflows. Use when the user wants to interact with TeamSupport data.
Teamtailor integration. Manage data, records, and automate workflows. Use when the user wants to interact with Teamtailor data.
TeamWave integration. Manage Organizations, Pipelines, Users, Filters. Use when the user wants to interact with TeamWave data.
Teamwork integration. Manage Organizations, Users. Use when the user wants to interact with Teamwork data.
Teamwork CRM integration. Manage Deals, Persons, Organizations, Leads, Projects, Activities and more. Use when the user wants to interact with Teamwork CRM data.
Teamwork Desk integration. Manage Organizations. Use when the user wants to interact with Teamwork Desk data.
Automatically look up Teamwork task status, details, or project information when user mentions ticket numbers, asks "what's the status of", or needs quick project context.
Automatically create properly formatted Teamwork tasks when user provides task details, mentions creating tickets, or shares work that needs tracking.
TecAlliance integration. Manage data, records, and automate workflows. Use when the user wants to interact with TecAlliance data.
Negotiation frameworks for technology services agreements, B2B contracts, and professional services deals. Use when reviewing or negotiating tech contracts.
Skill pro psaní kvalitní technické dokumentace k softwarovým projektům (uživatelské příručky, administrátorské příručky, vývojářské příručky, popisy datových formátů).
التقنية وبناء المنتج في السوق المصري — مواهب التقنية، الـ stack الشائع، تأثير تذبذب العملة على التكاليف السحابية، بدائل الاستضافة المصرية، وقالب pipeline التوظيف.
パーソナライズされた技術ニュースの自動収集・整理コマンド。 日本語（Zenn、はてブ、Qiita）と英語（Hacker News、Lobsters、Dev.to）の 情報源からユーザーの技術スタックに関連するニュースを収集し、 カテゴリ別・重要度順に整理してMarkdownドキュメントにまとめる。 トリガー: 技術ニュース, tech news,…
掃描資訊業相關新聞網站（Hacker News、Martin Fowler、The New Stack、High Scalability、iThome），依使用者指定的時間區間抓取後端、架構、雲端、AI 等領域的最新文章，整理重點摘要並翻譯成繁體中文，標題保留原文附翻譯，每篇 3~5 個重點，附原文連結，輸出為 .md 與 .docx…
Use when the user says /tech-radar or asks to evaluate, adopt, or compare a technology, framework, or tool for formal adoption.
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…
Automated technical writing style and quality enforcement. Lint documentation with Vale, check for inclusive language, enforce style guides, and analyze readability metrics.
Find and eliminate technical debt — duplicated code, dead code, redundant abstractions. Use at the end of a coding session or when the codebase feels bloated.