322건 · 관련도순
Audit structural debt, logic leakage, and monolithic components across Web, Mobile, and Backend codebases. Use when reviewing architecture, assessing tech debt, detecting logic in wrong layers, or identifying God classes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze Elixir/Phoenix technical debt — duplicates, refactoring; Use when asked about code quality, cleanup, or what…
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Harvest every `honey:` shortcut marker into a debt ledger, flagging the ones with no revisit trigger. One-shot report, changes nothing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Harvest honey shortcut markers into a debt ledger.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when asked to organize finances, create a budget, plan debt payoff, build savings goals, audit subscriptions, or do any personal money management task. Triggers on "budget", "finances", "savings", "debt", "subscriptions", "emergency fund", "investing", "cash flow", "money system", "financial plan".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect and analyze areas with high maintenance cost, poor design, or accumulated technical debt. Use this skill when reviewing codebases for quality issues, planning refactoring efforts, conducting code audits, assessing project health, identifying maintenance hotspots, or prioritizing technical improvements. Analyzes code smells, architectural issues, dependency problems, test quality, documentation gaps, and provides actionable recommendations with priority rankings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants to simplify, clean up, refactor, tidy, or refine code — their staged/unstaged git changes or a target file/path. Reduces complexity, flattens nesting, removes redundancy and dead code, scores each change by value (holding low-value churn), then runs tests to prove nothing broke. Invoke on: "simplify", "simplify this", "simplify my code/changes", "clean up", "clean this up", "clean up my changes", "refactor this", "make this cleaner", "tidy this up", "reduce complexity", "flatten this", "remove dead code", "make it more readable", "polish before commit", or "absolute simplify". Acts on your working diff; for repo-wide dead code use absolute-prune; for lint/type debt use absolute-debt.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user wants to build a financial model — 3-statement model, DCF valuation, LBO, SaaS unit economics, sensitivity / scenario analysis, debt schedule, or fundraising projections — in Excel. Trigger on: 'financial model', '3-statement model', 'P&L + BS + CF', 'DCF', 'WACC', 'NPV', 'terminal value', 'LBO', 'debt schedule', 'cash sweep', 'MOIC', 'IRR / XIRR', 'sensitivity table', 'scenario analysis', 'ARR model', 'unit economics', 'CAC / LTV', 'cap table forecast'. Output is a single formula-driven .xlsx. This skill is a scene layer on top of officecli-xlsx — it inherits every xlsx v2 rule (4-color code, visual floor, number formats, cache-drift, Known Issues, Delivery Gate minimum cycle). DO NOT invoke for a simple budget tracker, CSV dump, or operational KPI sheet — route those to officecli-xlsx base.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified backlog to 10-day sprint cadence to veto power rules. What's inside: • Dual-layer Kanban system (master backlog + sprint board with unified tagging) • 10-day sprint standard process (Day 1 dev → Day 6 testable build → Day 10 ship) • Issue template with reproducibility requirements (3x reported = auto-severe) • Tri-party alignment meetings (daily standup / sprint planning / sprint review) • Operations veto power on releases (P0 bug = block shipping) • User feedback → product iteration closed loop (beta testing + interview SOP) • Core metrics framework (acquisition → activation → retention → monetization → referral) • Technical debt management (20-30% sprint capacity reserved) • Ready-to-use templates: Bug Report, Sprint Planning, Responsibility Matrix Built from: Real product strategy meetings + beta testing frameworks. References Supabase sprint model, Manus/DeepSeek commercialization alignment. By @WeiYipei. 🇨🇳 你的研发团队在做没人要的新功能，用户反馈的 Bug 堆了三个月没人动。运营觉得研发不听用户，研发觉得运营不懂技术。这份 SOP 给你从统一看板到 10 天迭代节奏到一票否决权的完整产研运协同框架。 🇯🇵 開発チームは誰も求めていない機能を作り、ユーザーから報告されたバグは何ヶ月も放置。このSOPは、統一バックログから10日スプリント、リリース拒否権まで、プロダクト×エンジニアリング×オペレーションの完全な連携フレームワークを提供します。 🇰🇷 개발팀은 아무도 요청하지 않은 기능을 만들고, 사용자가 보고한 버그는 몇 달째 방치됩니다. 이 SOP는 통합 백로그부터 10일 스프린트, 릴리스 거부권까지 제품×개발×운영 완전 협업 프레임워크를 제공합니다. Triggers: "product ops" | "engineering operations" | "product development SOP" | "sprint planning" | "iteration management" | "cross-functional alignment" | "product engineering ops" | "dev ops collaboration" | "产研运协同" | "迭代管理" | "产品研发运营" | "プロダクト開発運営" | "제품개발운영"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert-level personal financial planning and wealth building. Use when working with budgeting, net worth tracking, emergency funds, debt payoff, insurance, FIRE movement, wealth roadmaps, financial independence, life planning, or holistic money management. Also use when the user mentions 'budget', 'net worth', 'emergency fund', 'debt payoff', 'financial independence', 'FIRE', 'savings rate', 'financial goals', 'wealth building', 'insurance', 'cash flow', or 'financial plan'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Personal finance assistant for budgeting, savings goals, investment tracking, debt optimization, tax preparation, insurance review, net worth tracking, and financial scenario modeling. Supports multi-currency, bank statement import (CSV/MT940/OFX), and locale-based tax rules. Use for any personal finance question: budget planning, expense tracking, portfolio allocation, FIRE calculations, debt payoff strategies, mortgage comparisons, tax deductions, insurance coverage, retirement planning, and life events with financial impact such as marriage, buying a house, changing jobs, having a baby, or going freelance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Survey a codebase for accessibility debt — missing ARIA, broken keyboard patterns, and contrast issues. Use when asked "how accessible is our codebase", "find accessibility debt", or "where are our a11y gaps".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when asked to analyze a file, a directory, or the whole codebase to understand structure, architecture, dependencies, complexity, duplication, dead code, or technical debt — e.g. "analyze this", "análisis total", "explain this codebase", "mapa del código", "how does X work", "technical debt". Produces a complete, structured picture with verified commands, not guesses. Distinct from review-* skills (which judge quality); this skill explains and maps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Personal finance assistant for budgeting, savings goals, investment tracking, debt optimization, tax preparation, insurance review, net worth tracking, and financial scenario modeling. Supports multi-currency, bank statement import (CSV/MT940/OFX), and locale-based tax rules. Use for any personal finance question: budget planning, expense tracking, portfolio allocation, FIRE calculations, debt payoff strategies, mortgage comparisons, tax deductions, insurance coverage, retirement planning, and life events with financial impact such as marriage, buying a house, changing jobs, having a baby, or going freelance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when auditing the imp codebase for structural debt, dead code, god-objects/files, duplication, flag sprawl, or deciding whether a cleanup is worth shipping - "structure audit", "tech debt", "is this still used", "dead code", "refactor for clarity", "should we split this file", "remove this flag", "file size gate red", "alloc sites gate red". Do NOT use for build/test mechanics (building-and-testing), perf/kernel work (benchmark-cuda / sm120-cuda-expert), or output quality (check-degeneration).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds project finance models with construction period draws, operational cash flows, DSCR covenants, and sculpted debt repayment. Use when modeling project finance, calculating debt service coverage, or structuring project lending.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coordinates private placement execution with investor targeting, NAIC designation analysis, and shelf registration requirements. Use when managing PP offerings, targeting insurance company investors, or structuring private notes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluates local currency government and corporate bond markets with yield analysis, inflation dynamics, and FX carry assessment. Use when analyzing local currency debt, evaluating EM bond opportunities, or assessing carry strategies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
"Apply the Modigliani-Miller theorem to analyze capital structure decisions and identify when financing choices affect firm value. Use this skill when the user needs to evaluate debt-equity tradeoffs, assess the impact of leverage on firm value, understand tax shield benefits, or when they ask 'does capital structure matter', 'should we take on more debt', or 'what is the optimal leverage ratio'.".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a task needs the judgment of a bill and account collector — prioritizing a delinquent-account portfolio by recovery likelihood, structuring a payment plan against a debtor's stated ability to pay, drafting an FDCPA/Reg F-compliant collection communication, handling a cease-and-desist or debt dispute, or deciding when an account should be written off or referred to legal.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inventory and prioritize all technical debt in a codebase. Scans for TODO/FIXME/HACK markers and stale comments, outdated and deprecated dependencies with CVE detection, high-churn files and cyclomatic complexity hotspots, duplicated code blocks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze debt payoff software — avalanche vs snowball strategy engines, interest calculation accuracy, amortization schedules, payment scheduling automation, credit score impact modeling, hardship accommodation workflows, and progress visualization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.