333 件 ・ 関連度順
概要と使いどころ
Apply the Law of Figure-Ground — establish which layer is foreground and actionable versus background. Use when designing modals, overlays, and depth. For emphasising one element among peers, use `von-restorff-effect`.
日本語の概要は準備中です。原文の説明を表示しています。
Configures Amazon CloudFront content delivery across six workflows: when to use CloudFront and how it fits with AWS WAF, Shield, CloudFront Functions, Lambda@Edge, Route 53, and origins (creating a distribution, caching, and Flat Rate Pricing (FRP) versus pay-as-you-go pricing); managing custom-domain TLS certificates (ACM in us-east-1); configuring multi-tenant distributions; protecting origins with origin access control (OAC), VPC origins, and origin mutual TLS (mTLS); securing content with signed URLs and cookies, geographic restrictions, viewer mutual TLS, and edge token validation; and observing traffic with standard and real-time logs. Applicable when the customer wants to put CloudFront in front of content, choose pricing, lock an origin, restrict who can view content, or analyze logs. Not applicable for the Route 53 DNS side of a CloudFront custom domain or failover between distributions (see the route53-cloudfront skill), or for pure-Route 53 DNS work (see the route53 skill).
日本語の概要は準備中です。原文の説明を表示しています。
Configure AssemblyAI keys, regional endpoints, and server-versus-browser authentication safely. Use when installing or authenticating an integration. Trigger with "AssemblyAI auth", "AssemblyAI API key", or "AssemblyAI endpoint setup".
日本語の概要は準備中です。原文の説明を表示しています。
Guided journey from an app idea to a deliberate architecture: boundaries, domain model, data decisions, and resilience, making only the expensive-to-reverse decisions and deferring the rest. Orchestrates eight skills phase by phase - clean-architecture, domain-driven-design, system-design, ddia-systems, software-design-philosophy, release-it, pragmatic-programmer, 37signals-way - asking the user questions at every decision point and recording results in the project docs/ folder (ARCHITECTURE.md, DESIGN-CODE-ARCHITECTURE-PLAN.md) so the journey resumes across sessions. Use when the user wants to design a new app's architecture, choose boundaries and a domain model, decide monolith versus microservices, or says 'how should I structure this app'. If a codebase already exists, use remove-technical-debt (aged), improve-code-quality (fresh prototype), or architecture-optimization (slow but working); if unvalidated, run create-business or create-app first. For one framework in isolation, invoke that skill directly.
日本語の概要は準備中です。原文の説明を表示しています。
Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. Use this for build-versus-buy calls, technology selection, architectural direction, engineering capacity and delivery risk, technical debt tradeoffs, platform and tooling decisions, or when a technical choice has business consequences that need stating in business terms. Also use to judge whether a technical plan is sound before it is committed to.
日本語の概要は準備中です。原文の説明を表示しています。
Covers the employment rules that carry real penalties — exempt and non-exempt classification, overtime and hours, employee versus contractor status, work authorization and recordkeeping, accommodation requests, and the notices and retention obligations that go with them. Use this to classify a role, review a contractor arrangement, respond to an accommodation request, work out what records to keep and for how long, or sanity-check a practice you inherited.
日本語の概要は準備中です。原文の説明を表示しています。
Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget. Use this to build a hiring plan, decide which roles to open and in what order, model attrition and backfill, plan for a growth or contraction scenario, or connect headcount plans to the budget.
日本語の概要は準備中です。原文の説明を表示しています。
The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost center rather than an enabler.
日本語の概要は準備中です。原文の説明を表示しています。
Owns data as an asset — governance, quality, the warehouse and semantic layer, analytics capability, and the governance of models built on top. Use this for a decision about how data is collected, stored, defined, or shared; when numbers disagree between teams; when deciding what to build in-house versus buy; when standing up a data function; or when an AI or model decision needs governance rather than engineering.
日本語の概要は準備中です。原文の説明を表示しています。
Builds and operates data pipelines — ingestion, transformation, orchestration, quality testing, and reliability of data delivery. Use this to design or debug a pipeline, decide batch versus streaming, add data quality checks, handle late or duplicate data, or work out why a dashboard's numbers changed without anyone changing the dashboard.
日本語の概要は準備中です。原文の説明を表示しています。
Builds the help center, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability, maintenance, and deflection measurement. Use this to build or fix a help center, reduce support volume, write documentation for customers, improve findability, or decide what deserves a help article versus a product fix.
日本語の概要は準備中です。原文の説明を表示しています。
Decides how the business is financed and what that financing then requires of it — debt versus equity, weighted average cost of capital as a hurdle rate, how much leverage cash flow can carry, and the financial, affirmative and negative covenants, definitions, test dates and cure rights that come attached. Use this to evaluate a financing option, set an investment hurdle, check whether a planned decision will trip a covenant, or work out what a lender can do when one breaks.
日本語の概要は準備中です。原文の説明を表示しています。
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
日本語の概要は準備中です。原文の説明を表示しています。
Runs corporate development — deal thesis, target screening, valuation framing, diligence, and integration planning. Use this when considering an acquisition or being approached about one, when evaluating build-versus-buy at company scale, when running or reviewing diligence, or when planning how an acquired business will actually be integrated.
日本語の概要は準備中です。原文の説明を表示しています。
Extends a mechanistic or association-level biomedical finding into a staged validation pathway that moves from descriptive evidence toward stronger functional support, mechanistic specificity, and clinical relevance. Use this skill when a user has a pathway, biomarker, cell-state, target, mechanism, or association finding and needs to decide what should be validated next, in what order, and which evidence layers are necessary versus optional. Do not default to maximal validation stacks. Build a structured validation ladder with a primary route, stronger upgrade route, and optional extensions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when estimating immune infiltration from bulk RNA-seq expression matrices with ssGSEA/GSVA, comparing case versus control groups, and generating downstream immune-score visualizations. NOT for single-cell RNA-seq, absolute cell proportion estimation, or clinical decision making.
日本語の概要は準備中です。原文の説明を表示しています。
Draft and submit evidence-backed XQUIC GitHub bug issues in the repository's CONTRIBUTING and issue-template format. Use when preparing or opening an alibaba/xquic issue that must identify an exact RFC or draft mechanism, expected-versus-actual behavior, reproduction evidence, and optional verified source root cause; requires issue-check to return true before any GitHub submission.
日本語の概要は準備中です。原文の説明を表示しています。
Use when evaluating markets through Howard Marks-style second-level thinking, credit cycles, risk premiums, market psychology, and defensive versus aggressive posture.
日本語の概要は準備中です。原文の説明を表示しています。
Redesign GitHub README homepages or create project-native pure SVG, hybrid SVG-composed PNG/WebP, and opt-in animated GIF assets. Use when a user asks to beautify, redesign, rebrand, visually upgrade, simplify, or audit a GitHub README; create only a hero, section headers, diagrams, badges, motion graphics, showcase modules, or other README assets; or turn a repository homepage into a cohesive visual story. If whole-README work versus asset-only work is unclear, ask which scope the user wants. For hero-like assets where pure SVG and generated raster material are both viable, explain the tradeoffs and confirm the implementation before creating the asset.
日本語の概要は準備中です。原文の説明を表示しています。
Before committing scarce time, people, or money, name the best forgone use of those resources and the value delta of the chosen path versus that alternative.
日本語の概要は準備中です。原文の説明を表示しています。
Run a Google Alerts-style keyword coverage tracker. Uses news-search for recent keyword queries, lets the LLM dedupe and classify real features versus junk, stores decisions in SQLite, and alerts only on new real coverage.
日本語の概要は準備中です。原文の説明を表示しています。
DataOps and DS/MLOps testing reference for data tiering, Bronze-to-Silver validation placement, pipeline invariants, pytest categories, and validation-versus-drift. Use when designing, reviewing, or generating data pipelines, transformation code, data validation, or data-science test suites.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked 幼升小怎么准备, 小升初流程, 入学信息采集, 学区房和多校划片, 公民同招, 民办摇号, 随迁子女入学, 居住证入学材料, or plan a child's entry to primary or junior high school in mainland China. Produces a month-by-month timeline for the child's city, the documents to prepare (户籍, 房产 or 租房, 居住证, 社保), the questions to ask the 教育局 or school about 学区, 多校划片 and 派位, a public versus private comparison, and a checklist, with every local rule marked to confirm with the local education bureau.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked 年终奖怎么算, 13薪和年终奖有什么区别, 年终奖怎么交税, 单独计税还是并入综合所得, 年终奖被扣了怎么办, 离职了年终奖还发吗, 怎么问 HR 年终奖, or understand a year-end bonus in mainland China. Produces how the person's bonus is likely calculated from their documents, the 13薪 versus discretionary bonus distinction, the tax options with a worked comparison marked to confirm, questions to ask HR or the manager in writing, and the steps if a bonus is withheld after resignation, all marked to confirm against current rules. Not tax or legal advice.
日本語の概要は準備中です。原文の説明を表示しています。