MaybeMonad

@maybemonad source repo

18 skills
0 followers
1 day ago last updated

▌
Technical SEO · maybemonad
Technical SEO workflow for canonical metadata, public routes, redirects, sitemap, robots.txt, structured data, image alt text, SSR crawlability, indexing submission, and public discoverability. Use when changing SEO copy, route canonicals, search visibility, crawler access, sitemap inventory, IndexNow, Google Search Console, or Bing Webmaster Tools.

0
installs
▌
Blindspot · maybemonad bundle
Pre-implementation blind spot pass for finding unknown unknowns before agentic coding, design, research, or domain work. Use when the user says blindspot pass, unknown unknowns, help me prompt better, I am new to this codebase/domain, I do not know what questions to ask, or wants relevant risks, hidden constraints, and cheap probes before implementation.

0
installs
▌
Web Clone · maybemonad bundle
Website cloning and web-effect reconstruction workflow. Use when the user says clone this website, reproduce this site, rebuild this page, reverse-engineer a WebGL/Canvas/Three.js effect, copy a website for local learning, visual clone, content remix, 复刻网站, 克隆网站, 抄个站, 仿站, 照着这个站做一个, or 把这个站搬下来改成我的.

0
installs
▌
Design Polish · maybemonad bundle
Design polish quality gate for completed or near-completed UI, prototypes, pages, decks, screenshots, dashboards, or app screens. Use before handoff, shipping, stakeholder review, app-store capture, or when checking accessibility, hierarchy, interaction states, responsiveness, and AI-template tropes.

0
installs
▌
Change Quiz · maybemonad bundle
Post-implementation learning and quiz workflow for making the user understand a code change before merge, release, review, or handoff. Use when the user asks for a quiz, wants to understand what changed, says merge only when I pass, or needs a report with context, intuition, behavior, risks, and verification followed by comprehension questions.

0
installs
▌
Design Workflow · maybemonad bundle
Design workflow router for UI, page, app screen, prototype, deck, design-system, visual-direction, variation, or polish work. Use when the user asks for design help and the next step may be source-map extraction, aesthetic direction, options, prototyping, or final quality review.

0
installs
▌
Design Direction · maybemonad bundle
Aesthetic direction workflow for greenfield UI, brandless screens, new visual systems, redesign concepts, or designs that need a concrete typography, color, density, component, imagery, and motion thesis before hi-fi work.

0
installs
▌
Design Prototype · maybemonad bundle
Interactive design prototype workflow for clickable flows, mockups, demos, app screens, stateful UI, form validation, loading/error/success feedback, keyboard behavior, and design handoff prototypes.

0
installs
▌
Design Source Map · maybemonad bundle
Source-map extraction for design systems, brands, UI kits, screenshots, Figma files, existing codebases, reference sites, tokens, components, layout grammar, and visual vocabulary. Use before matching or extending an existing design.

0
installs
▌
Design Variations · maybemonad bundle
Design variation workflow for options, alternatives, wireframes, multiple takes, visual explorations, layout comparisons, flow comparisons, or taste discovery before committing to one direction.

0
installs
▌
Pitch Explainer · maybemonad bundle
Post-implementation pitch and explainer workflow for packaging a prototype, spec, implementation notes, verification evidence, and resolved unknowns into a reviewer-ready document. Use when the user asks for a Slack-ready summary, buy-in doc, explainer, launch note, approval packet, or wants reviewers to see the context, demo, decisions, tradeoffs, and remaining risks.

0
installs
▌
Interview Unknowns · maybemonad bundle
Clarifying interview workflow for resolving ambiguities that can change architecture, data models, APIs, UX flows, acceptance criteria, or implementation scope. Use when the user asks to be interviewed, says ask me questions, says there are still unknowns, or when a small number of user answers would materially change the plan.

0
installs
▌
Reference Alignment · maybemonad bundle
Reference-driven requirement extraction for behavior, design, architecture, workflows, or domain semantics that are hard to describe from scratch. Use when the user points to source code, a folder, docs, screenshots, diagrams, websites, examples, prior implementations, libraries, or says they cannot describe what they want but can provide a reference.

0
installs
▌
Brainstorm Prototype · maybemonad bundle
Pre-implementation brainstorming and disposable prototyping for unknown knowns, taste, product direction, UX layout, visual design, workflow choices, and solution discovery. Use when the user says brainstorm, prototype before wiring, show options, I will know it when I see it, I do not know what is possible, or wants multiple approaches before touching durable app code.

0
installs
▌
Implementation Notes · maybemonad bundle
During-implementation notes workflow for logging decisions, deviations, edge cases, conservative choices, evidence, and open questions while an agent implements a plan. Use when the user asks to keep implementation-notes.md or notes, when unknowns may appear during implementation, when the plan may need to change, or when a future attempt should learn from this run.

0
installs
▌
Map Territory Workflow · maybemonad bundle
Full development workflow for matching the user's prompt or plan to the real codebase, domain, runtime, and constraints. Use when the user wants a complete unknowns-reduction process across before, during, and after implementation; asks for map vs territory thinking; wants to choose among blindspot pass, brainstorm/prototype, interview, references, implementation plan, implementation notes, pitch/explainer, or quiz; or needs a long-horizon agentic coding process that handles unknowns iteratively.

0
installs
▌
Implementation Plan Review · maybemonad bundle
Implementation planning workflow focused on the decisions most likely to change before coding starts. Use when the user asks for an implementation plan, plan in HTML, review the plan before implementation, focus on data models, type interfaces, UX flows, architecture choices, validation gates, or wants to reduce rework before touching code.

0
installs
▌
Orchestrate Codex Workflow · maybemonad bundle
Robust Codex orchestration workflow for complex implementation, planning, debugging, or audit tasks that need v1 planning, adversarial loophole checks, frozen execution specs, task ledgers, optional executor delegation, browser or command-line quality gates, fix loops, and final evidence-backed reports. Use when the user asks Codex to be autonomous, plan then execute, coordinate other executors such as DeepSeek or Kimi, harden a strategy until confident, run deep quality checks, continue through context loss, or avoid quitting in the middle of a multi-step task.

0
installs

18 published skills