614건 · 관련도순
Consolidate all SAST vulnerability results from the sast/ folder into a single final report ranked by severity and confidentiality impact. Reads all *-results.md files and produces sast/final-report.md. Run after all vulnerability detection skills complete. Use when asked to generate a final report, consolidate findings, or summarize security results.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convert English-language properties in PROPERTIES.md (produced by the Fizz skill) into Solidity assertions inside the existing fuzz harness, then flip their checkboxes. Trigger on "fizz-convert", "convert properties", "implement properties from PROPERTIES.md", "convert PROPERTIES.md to Solidity".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Security audit of Solidity code while you develop. Trigger on "audit", "check this contract", "review for security", "loop mode", "run the auditor in loop mode", "run 3 passes". Modes - default (full repo) or a specific filename. Loop mode runs several passes in one scan, each pass told what the earlier ones found, and ends in one combined report; it remembers findings between scans in a ledger.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to configure canonical URLs, fix duplicate content, or consolidate URL signals. Also use when the user mentions "canonical," "canonical URL," "duplicate content," "duplicate content fix," "preferred URL," or "URL consolidation." For GSC duplicates, use google-search-console.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit and reduce infrastructure and tooling costs without sacrificing reliability or velocity. Use this skill when reviewing monthly cloud or SaaS spend, finding unused resources, rightsizing infrastructure, negotiating vendor contracts, deciding what to consolidate, or planning for budget cuts. Triggers on cost optimization, cloud spend, SaaS spend, rightsizing, unused resources, FinOps, infrastructure audit, vendor consolidation, budget cut, cost review. Also triggers when finance flags rising costs or when a contract renewal is up.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Move content between platforms, domains, or URL structures while preserving SEO equity, user bookmarks, and integrations. Use this skill when planning a CMS migration, replatforming, consolidating sites, changing URL structures, or merging content from multiple sources. Triggers on content migration, replatform, CMS migration, domain migration, URL restructure, redirect map, site merge, content consolidation, migration plan, post-migration drop. Also triggers when planning a launch that involves moving existing content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stage exploration before instruction on complex problems. The learner produces two attempted approaches before consolidation — which builds on those attempts, not from scratch. Use for genuinely hard problems where struggle produces deeper learning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit a project's infrastructure and SaaS stack, then produce a cost report showing what the user currently pays and what they would save by consolidating onto Temps (self-hosted or Temps Cloud). Detects hosting platforms (Vercel, Netlify, Railway, Render, Heroku, Fly.io), analytics (PostHog, Plausible, Mixpanel, Amplitude, Fathom), error tracking (Sentry, Bugsnag, Rollbar, Honeybadger), session replay (LogRocket, FullStory, Hotjar, Highlight), uptime monitoring (Pingdom, UptimeRobot, Better Stack, Checkly), managed databases (Supabase, Neon, PlanetScale, MongoDB Atlas, Upstash, RDS), and transactional email (SendGrid, Postmark, Resend, Mailgun) from dependencies, config files, and env var names. Use when the user wants to: (1) Know how much they would save by switching to Temps, (2) Audit their SaaS/infrastructure spend, (3) Compare their current stack's cost against self-hosting, (4) Decide whether Temps is worth it, (5) Build a business case for consolidating tools. Triggers: "how much would I save", "temps savings", "cost comparison", "audit my stack", "am I overpaying", "saas spend", "calculate savings", "is temps cheaper".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SOLID principles checklist with Java examples. Use when a class has too many responsibilities, an abstraction leaks, or a dependency points the wrong way, and when the user asks about Single Responsibility, Open/Closed, Liskov, Interface Segregation or Dependency Inversion. For naming, duplication and method length, use clean-code instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Consolidate IBRK trade CSV files from a directory into a summary report. Groups trades by symbol, underlying, date, strike, buy/sell, and open/close. Outputs both markdown and CSV.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
TypeScript, JavaScript, Python, Go, Swift, Kotlin対応のコードレビュー自動化スキル。 PRの複雑度・リスク分析、SOLID違反・コードスメルの検出、レビューレポート生成。 「コードレビューして」「PRを分析」「コード品質チェック」「レビューレポート」等のリクエストで発動。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert in Ethereum Virtual Machine internals - gas optimization, assembly/Yul, opcode-level optimization, and low-level EVM patternsUse when "evm, gas optimization, yul, inline assembly, opcodes, solidity optimization, evm bytecode, storage layout, evm, ethereum, solidity, yul, assembly, gas-optimization, opcodes, smart-contracts" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when modelling a rich domain in Java - SOLID principles, encapsulated entities that enforce their own invariants, and value objects over primitives
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stage exploration before instruction on complex problems. The learner produces two attempted approaches before consolidation — which builds on those attempts, not from scratch. Use for genuinely hard problems where struggle produces deeper learning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Software architecture guidelines to maintain code readability (Clean Code, SOLID, DRY) and application scalability / Panduan arsitektur perangkat lunak untuk menjaga keterbacaan kode (Clean Code, SOLID, DRY) dan kemampuan skalabilitas aplikasi.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debt payoff strategy generator. Compares avalanche (highest interest first) vs snowball (smallest balance first) methods, calculates payoff timelines and total interest saved, and recommends optimal payment allocation across multiple debts. Includes credit card consolidation and refinancing analysis. Use when the user says "/finance debt", "pay off my debt", "snowball or avalanche", "consolidation", or asks for any debt strategy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Software design principles, patterns, and architecture from SOLID through distributed systems. Covers the five SOLID principles with violations and fixes, DRY/KISS/YAGNI heuristics, separation of concerns, 12 GoF design patterns organized by intent (creational, structural, behavioral), architectural patterns (MVC, MVP, MVVM, layered, hexagonal, microservices, event-driven), coupling and cohesion metrics, dependency injection, and the design decision framework for choosing between competing approaches. Use when making design decisions, reviewing architecture, refactoring code, or teaching software engineering principles.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use at write time to vector/embedding memory — Grove content-addressed insertion, chroma/pgvector upserts, memory-consolidation promoting session traces to MEMORY.md, or embedding externally-ingested content. Scores each candidate record against a fixed panel of sentinel queries and quarantines any record that would become the nearest neighbor of too many unrelated queries — a hub — whether from adversarial poisoning or accidental over-generality. This is the memory-record-side sibling of skill-injection-guardian (file-side) and the write-side complement of memory-use-warrant (read-side). Quarantine, never silently drop; a human reviews. Backed by the admission-time hubness gate (arxiv 2606.19692v1). Triggers on inserting into vector memory, consolidating memory, and embedding stranger content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Single-pass SOLID review — dispatches one reviewer over the complete ruleset, emitting the fixed candidate schema.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ensemble SOLID review — fans the ruleset across overlapping focused workers over the same code, then reduces by corroboration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[AUTO-INVOKE] MUST be invoked BEFORE writing or modifying any Solidity contract (.sol files). Covers private key handling, access control, reentrancy prevention, gas safety, and pre-audit checklists. Trigger: any task involving creating, editing, or reviewing .sol source files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[AUTO-INVOKE] MUST be invoked BEFORE writing or modifying any test files (*.t.sol). Covers test structure, naming conventions, coverage requirements, fuzz testing, and Foundry cheatcodes. Trigger: any task involving creating, editing, or running Solidity tests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[AUTO-INVOKE] MUST be invoked BEFORE writing or modifying any Solidity contract (.sol files). Covers pragma version, naming conventions, project layout, OpenZeppelin library selection standards, oracle integration, and anti-patterns. Trigger: any task involving creating, editing, or reviewing .sol source files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
设计代码规范 / Lint 配置 / Code Review 标准时使用。覆盖 SOLID 原则 / Lint 工具（ESLint / Prettier / Checkstyle / pylint / golangci-lint）/ SonarQube 集成。融合 Clean Code + Robert Martin SOLID + Code Review 文化。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.