Results for “pathway-pages”

Scaffold a new public page under the (public) route group, following project conventions for server components, tenant config, and shadcn/ui styling.

Organizes discovered pathway, portal, and theme content into a docs repository by copying new files, resolving duplicates, updating the README, and generating per-portal indexes.

Scans local repositories and a Supabase database to inventory all pathway, portal, and theme content, producing a categorized report organized by portal.

Publish presentations and web content to GitHub Pages. Converts PPTX, PDF, HTML, or Google Slides to a live GitHub Pages URL. Handles repo creation, file conversion, Pages enablement, and returns the live URL.

Routes UI implementation or redesign to the narrowest build workflow for pages, apps, dashboards, and styled frontends.

Routes frontend design tasks to 48 specific UI styles, providing color palettes and implementation guidance for websites, app screens, or UI components.

Pulls pathway, book, course, article, and content item records from a Supabase database for the alan-hirsch tenant, organizes them by portal, and exports the results as markdown files into a local docs repository.

Generates a three-column technical documentation page with side navigation, article body, and sticky table of contents.

Scaffold a new page from the site's template system (e.g., new course landing page)

Page components — the thin data-fetching layer that binds a route to a template, invoking getServerSideProps/getStaticProps and passing props down. Use when creating a new route, choosing SSR vs SSG vs ISR for a page, or reviewing whether a page is doing template-level work it shouldn't.

Configures and troubleshoots the Salesforce Path component, including key fields, guidance text, confetti, and page placement.

Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services.

Detects all languages used on a webpage — both declared (html@lang, hreflang, nested lang=, meta content-language) and actually present in the body text using Google CLD3 WASM. Reconciles the two signal sets and flags mismatches for i18n audits, hreflang validation, and multilingual content verification.

Detects and removes disruptive overlays (cookie banners, modals, paywalls, login walls) from webpages before screenshots, scraping, or browser automation.

Route design-generation work into the right Open Design workflow mode — prototype, deck, document, or media artifact. Use when the user needs local-first UI prototype generation, presentation deck creation, or design-system-aware HTML/PDF/PPTX artifacts via locally-installed coding agents. Supports 72 built-in design systems, 5 visual directions, 93 media prompt templates, and multi-format export. Triggers on: open-design, local design tool, prototype generation, design deck, design artifact, design agent workflow, open design prototype, design system artifact, UI prototype generation.

Build a complete marketing plan covering the full customer journey from stranger to raving fan using a 9-square grid framework.

Create OR review a page-brief — the artifact BETWEEN a wireflow and the full PRD. It turns each unique page/screen of a product into documented requirements TIED TO JOBS: a self-contained board card per page (what the page is accountable for, the job-tagged checklist of what it must let you do, the journeys it appears in, what it connects to, and the acceptance criteria that say how you'd know it's right). It is the "PRD per page", not a sitemap — and it stops ABOVE the screen: no components, no layout, no hierarchy. Use whenever the user wants to "spec the pages", "document each screen", turn a wireflow + live design into per-page requirements, or asks "what does this page need to do / which jobs pass through it" — even if they never say "page-brief". Natural NEXT STEP after the wireflow skill. ALSO use it to REVIEW an existing page-brief / screen catalog. In the A-Team pipeline this is a definition-phase skill: output lands in docs/features/<slug>/briefs/pages/, job codes are the durable [[NN]] ids from doc

Scaffold a new mobile page/screen using the StyleSeed layout patterns

Page header component for page titles with navigation and content slots. Invoke when user needs page headers, breadcrumb navigation, or page title sections in Naive UI.

Creates Keynote-style presentations as single-page HTML slides with keyboard navigation, fade transitions, and a clean, minimal layout.

Plan website page hierarchy, navigation, URL patterns, and internal linking for improved SEO and user experience.

Publish static or dynamic HTML, websites, and web applications through QW Pages. Use when the user asks to publish, deploy, or make a webpage live. Combine with qw-pages-supabase only when the webpage needs persistent database storage.

Routes, controller, Acorn routes, web.php, route:list, Route::get, Route::post, Route::resource, Route::apiResource, middleware, route model binding, API endpoint, RouteServiceProvider, named routes, resource controller, single-action controller, invokable controller, route group, route prefix, JSON response, rate limiting, token auth, Accept application/json, route cache, WP rewrite conflicts — using Acorn's Laravel routing inside WordPress/Sage/Bedrock

Scaffold a new mobile page/screen using the StyleSeed layout patterns

Creates CodeTour `.tour` files with real file and line anchors for guided codebase walkthroughs, including onboarding, architecture, PR, and RCA tours.

Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests.

Discovers and lists all URLs on a website, with optional search filtering to find specific pages within large sites.

Generate a two-page digital e-guide spread with a cover and content page, including pull-quote and step list, in a lifestyle creator brand style.

Creates persona-targeted, step-by-step CodeTour walkthroughs that link to real files and line numbers for onboarding, architecture, PR review, and more.

Route web design, motion, WebGL, and visual-styling requests into the narrowest matching sub-skill of the 79-skill MengTo/Skills web-design family — Style/Design-System Packs, Full-Site Quality & Direction, Motion & Scroll Systems, WebGL/3D Backgrounds & Shaders, Library Embeds & Integrations, Component & State Effects, and CSS Technique Primitives. Use when picking and fetching the right visual recipe for a marketing site, landing page, portfolio, or dashboard shell, then combining layers in direction → layout → background → motion → component-state → polish order. Triggers on: web design, landing page, awwwards, GSAP, Lenis, scroll animation, WebGL background, shader, glass UI, dark mode design system, editorial layout, cursor trail, progressive blur, gradient border, three.js background, vanta, globe.gl, unicorn studio, marketing site polish.

Integrate Iteration Layer APIs for document, website, image, and sheet processing. Composable APIs — Document Extraction, Website Extraction, Document to Markdown, Image Transformation, Image Generation, Document Generation, and Sheet Generation — share one credit pool and chain together into workflows.

Creates a comprehensive end-to-end user journey map with stages, touchpoints, emotions, pain points, and opportunity areas for product design and UX analysis.

Route one Paperclip child stage of the PLE new-content routine, producing hash-verifiable evidence and a fail-closed handoff.

Use this skill for template SEO pages, data quality, index controls, duplicate prevention, scalable content QA. Trigger when the task involves seo work related to Programmatic SEO Pages, production implementation, audits, debugging, strategy, or validation.

Plan and blueprint programmatic SEO page strategies at scale