Results for “structure”

Convert various file formats (PDF, Office documents, images, audio, web content, structured data) to Markdown optimized for LLM processing. Use when converting documents to markdown, extracting text from PDFs/Office files, transcribing audio, performing OCR on images, extracting YouTube transcripts, or processing batches of files. Supports 20+ formats including DOCX, XLSX, PPTX, PDF, HTML, EPUB, CSV, JSON, images with OCR, and audio with transcription.

Sage theme with Acorn (Laravel IoC for WordPress) and Lando — lando start, lando info, lando acorn, Service Providers, View Composers, Blade components, ACF Composer blocks and fields, Poet CPT config/poet.php, AppServiceProvider, ViewServiceProvider, resources/views/, resources/css/app.css @theme Tailwind v4, resources/js/app.js, content/themes/{theme}/, lando yarn dev, lando yarn build, Blade @extends @section @include @component, Bedrock directory structure, lando wp, composer require, lando composer

Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.

Structured troubleshooting for Sage/Acorn/Lando projects — diagnoses PHP errors, Blade rendering failures, Livewire mount errors, Eloquent query issues, Acorn boot failures, queue job failures, WP hook conflicts; uses lando logs, Query Monitor, Xdebug, WP_DEBUG. Invoke for: "/debugging", "something is broken and I can't figure out why", "lando logs show an error", "acorn boot error", "blade is rendering wrong", "livewire component not mounting", "500 error", "debug this issue". Skip when: you are building or implementing features — that is /building, not debugging.

Convention audit and pre-PR code review for Sage/Acorn projects — checks PHP Blade JS CSS against Sage/Acorn/Tailwind v4 conventions; audits ACF Composer field patterns, Livewire component structure, Eloquent models, Acorn routes, Blade components; verifies design alignment; dispatches sage-reviewer agent; prepares code for PR merge. Invoke for: "review before PR", "run sage-reviewer", "convention audit", "/reviewing", "check my block for issues", "pre-merge review", "review this code". Skip when: you just need to read or understand a file — that is not a review session.

Swift language fundamentals (5.10+ / 6.x). Covers optionals, value vs reference semantics, protocols & generics, Swift Concurrency (async/await, actors, Sendable, structured tasks), Result Builders, and Apple platform interop. USE WHEN: user mentions "Swift", "SwiftUI", "async/await Swift", "actor", "Sendable", "Codable", "Combine", "Result Builder", "Apple Keychain", "Secure Enclave", "iOS native" DO NOT USE FOR: SwiftUI screen layouts in depth - use SwiftUI-specific skill if exists DO NOT USE FOR: Compose iOS via Skia - use `frontend-frameworks/compose-multiplatform` DO NOT USE FOR: Kotlin/Native ↔ Swift bridging - use `languages/uniffi`

Create professional, dark-themed SVG diagrams of any type — architecture diagrams, flowcharts, sequence diagrams, structural diagrams, mind maps, timelines, illustrative/conceptual diagrams, and more. Use this skill whenever the user asks for any kind of technical or conceptual diagram, visualization of a system, process flow, data flow, component relationship, network topology, decision tree, org chart, state machine, or any visual representation of structure/logic/process. Also trigger when the user says "画个图" "画一个架构图" "diagram" "flowchart" "sequence diagram" "draw me a ..." or uploads content and asks to visualize it. Output is always a standalone .svg file.

Build multiple genuinely different versions of a UI piece you describe, rendered behind a visual picker so you can flip through them live and promote the one that feels right. Use this proactively, without waiting to be asked, whenever evaluating a new feature, a layout, a section, a visual, a design, or any UI decision — divergent options beat a single guess. Fast, no interview, single-component scope. For a full structured exploration (interview, 5 variants of a whole page, real feedback collection, implementation plan) when the direction itself is still open, use `design-lab` instead — that one requires explicit invocation. Source: github.com/emilkowalski/skills.

Drive Moli (`moli`), Lexmount's open-source headless browser for AI agents, built around on-demand rendering: real JavaScript, DOM, and CSS by default, with layout and pixels computed only when explicitly requested via `--layout`. Use when the user wants to fetch/extract a live JavaScript-rendered page as Markdown/HTML/JSON/semantic-tree, capture a screenshot or PDF, run a small bounded crawl, start a CDP/WebDriver automation server for Playwright/Puppeteer, replace a Chromium/ChromeDriver dependency, or diagnose readiness/network/frame issues on a rendered page. Triggers on: "moli fetch", "moli serve", "headless browser for agents", "on-demand rendering browser", "CDP server without Chrome", "structure-first web scraping", "Lexmount browser", "moli-webfetch", "moli-cdp-server".

Structured threat modeling skill using the PASTA framework (Process for Attack Simulation and Threat Analysis) combined with Adam Shostack's 4-question framework. Use this skill whenever the user asks to do threat modeling, security analysis, map the attack surface, identify threats, or review an application for security risks — even if they don't mention PASTA or a specific framework by name. Core activities: Component Mapping (architecture + data flows), Critical Assessment (business impact prioritization), and Logic Flaw Identification (attacker mindset on business logic). Produces: component map diagram (Mermaid), data flow diagram (Mermaid), attack tree (Mermaid), STRIDE threat table, prioritized risk register, and an actionable mitigation plan. Invoke proactively for any security review, architecture review, or "what could go wrong?" session.

Conduct a design interview, generate 5 distinct UI variations in a temporary route, collect real click-to-comment feedback on the live rendered variants via human-review, and produce an implementation plan. Use when the user wants to explore UI design options, redesign an existing component/page, or create new UI with multiple genuinely different approaches to compare — before writing production code or committing to a direction. For a lighter, single-component variant picker with no interview, use `prototype` instead. For reviewing a UI that's already real (not exploring new directions), use `visual-review`. Source: adapted from github.com/0xdesign/design-plugin's design-lab skill (interview + 5-variant structure), with feedback collection replaced by this repo's own `visual-review` skill (human-review) instead of a bespoke overlay component.

Reconstruct a product flow, then audit how usable it is — whether it makes sense, where users get confused or stuck, whether the copy and instructions are clear, and where friction causes drop-off. Produces a prioritized, severity-weighted findings report. Works from three inputs: frontend code in a repo, a live running app driven via a browser, or a written flow / spec / screenshots. Use this skill whenever the user asks for a UX review, usability audit, "is this flow confusing", "does this signup/onboarding/checkout make sense", "why are people dropping off", "audit this form", "where's the friction", or hands over a flow and asks whether it's user-friendly. Trigger even on casual phrasings ("is my checkout any good?") — it imposes the structure ad-hoc UX opinions miss. Audits flow usability and friction; for visual polish and interface quality the impeccable audit/critique skills apply instead.