Results for “deepening”

Use when surfacing architectural friction and proposing deepening refactors (shallow modules → deep modules) for testability and AI-navigability. Triggers on "improve architecture", "find deepening opportunities", "where is this codebase shallow", "architecture review". Emits structured candidates + precise patches; delegates ALL rendering to mk:preview. NOT for diagram/HTML rendering (see mk:preview); NOT for trade-off deliberation (see mk:party); NOT for plan critique (see mk:plan-ceo-review).

The English summary is being prepared. Showing the original description.

Design modules that offer substantial behavior through a small interface, the rules callers must understand. Use shared design terms to simplify usage, contain complexity, choose where implementations can vary, and make behavior easier to test.

• Simplifying a module's interface
• Bringing scattered complexity into one module
• Choosing where implementations can be swapped

Improve architecture across modules by deepening interfaces.

The English summary is being prepared. Showing the original description.

Review a codebase for structural problems that make understanding and testing difficult. Compare refactoring candidates in an HTML report with before-and-after diagrams, then explore the chosen option through questions about constraints, design, and tests.

• Review architecture in frequently changed code
• Compare refactoring options with before-and-after diagrams
• Explore module designs that are easier to test

Design modules that hide complex behavior behind a small, clear interface. Use shared design principles to review dependencies, choose where behavior can be swapped, and make code easier to test and maintain.

• Simplifying a module's interface
• Reviewing where to separate responsibilities
• Designing code that is easier to test

Find opportunities to simplify a codebase by hiding complex behavior behind smaller interfaces. Compare candidates in a visual HTML report, then explore the chosen option through questions about constraints, dependencies, and testing.

• Finding structural improvements in frequently changed code
• Comparing refactoring candidates visually
• Exploring constraints and testing for a chosen candidate

Review module relationships and change history to identify structural improvements in a codebase. Receive ranked candidates with file references, suggested changes, and risks, plus a recommendation for where to start, without modifying code.

• Reviewing architecture after a batch of changes
• Investigating changes that touch too many files
• Prioritizing structural improvements

Research a topic from multiple angles, preserve sources according to your privacy preferences, and summarize each one. Combine the evidence into a self-contained reference page, including limitations and counterarguments, with options to deepen the research later.

• Building a reference guide on a new topic
• Keeping sources alongside individual summaries
• Comparing evidence, counterarguments, and limitations

Find suitable grants and bidding opportunities, check eligibility before drafting, and prepare applications or responses to requests for proposals using past submissions and actual organizational data. It also tracks submission deadlines and reporting obligations after an award.

• Finding grants your organization qualifies for
• Screening solicitations before deciding to bid
• Drafting applications from past submissions

Explore a codebase to find tightly coupled or fragmented modules, then compare interface designs that hide complexity behind simpler entry points. Produces a GitHub issue proposing a refactor, including dependency handling, testing impact, and design trade-offs.

• Finding architectural refactoring opportunities
• Consolidating tightly coupled modules
• Comparing interfaces for easier boundary testing

Korean and French screenwriting practice (韩国/法国编剧方法) — from the international masterclass; Oh Seung-uk (Christmas in August, The Shameless; field research in disguise, "write the emotion", first act and last act first, spaces as skeleton, reading to hostile listeners, surviving producers), Choi Seok-hwan (King and the Clown; genre as promise to the audience, "story = deepening crisis + intensifying desire", two reversals and bittersweet endings, the producer/director/writer trio), and Frédéric Auburtin (Paris je t'aime; dialogue last, Italian-style table reads, "12 lines not 13", dignity for characters, originals born from commissions, editing by emotion). Use when working in a Korean-style commercial drama or genre film, a French auteur/commission context, when planning field research, when a producer relationship is the problem, or when you need the Korean "three live together" development model or the French "emotion first, structure second" editing approach.

The English summary is being prepared. Showing the original description.

Lift a clickable card toward the viewer on hover with a deepening shadow — a tactile, responsive cue. Pure CSS, no JS. Only use on actually-clickable cards (motion implies clickability). Honors prefers-reduced-motion (static). Avoid on very dense grids where many lifts feel noisy.

The English summary is being prepared. Showing the original description.

Survey the codebase, pick ONE high-leverage deepening opportunity (filtering out anything already proposed), and publish it as a PRD-shaped GitHub issue via /to-prd-project. Designed to run unattended in the daily architecture-review workflow.

The English summary is being prepared. Showing the original description.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

The English summary is being prepared. Showing the original description.

Question-first approach to understanding user journeys. Load when starting a new journey design or when the discovery phase needs deepening.

The English summary is being prepared. Showing the original description.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

The English summary is being prepared. Showing the original description.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

The English summary is being prepared. Showing the original description.

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

The English summary is being prepared. Showing the original description.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

The English summary is being prepared. Showing the original description.

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

The English summary is being prepared. Showing the original description.

Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.

The English summary is being prepared. Showing the original description.

Scan a codebase for deepening opportunities, present them as a report — HTML on request — then grill through whichever one you pick.

The English summary is being prepared. Showing the original description.

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

The English summary is being prepared. Showing the original description.

Warren Buffett said he looks for "economic castles protected by unbreachable moats." A moat is a sustainable competitive advantage that protects your business from competitors. Without a moat, success attracts competition that erodes your margins to zero. This skill covers identifying, building, and deepening moats. Network effects, switching costs, brand, scale economies, and the rarer moats like regulatory capture and counter-positioning. Use when "moat, defensibility, competitive advantage, network effects, switching costs, barrier to entry, unfair advantage, protect from competition, sustainable advantage, winner take all, flywheel, lock-in, moat, defensibility, strategy, network-effects, switching-costs, competitive-advantage, seven-powers" mentioned.

The English summary is being prepared. Showing the original description.