Create Your First WordPress Plugin Using Cursor  🔗 **Source:** [Create Your First WordPress Plugin Using Cursor](https://www.youtube.com/watch?v=kb-sUyJhoWw) > [!note]+ Document Notes > tags: [wordpress-plugin-development, ai-assisted-coding, cursor-ide, wordpress-studio, plugin-monetization] > author: Ferdy Korpershoek > source: Ferdy Korpershoek (YouTube) > reference: https://www.youtube.com/watch?v=kb-sUyJhoWw > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: Create Your First WordPress Plugin Using Cursor (Complete Tutorial) > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Video: Create Your First WordPress Plugin Using Cursor](https://www.youtube.com/watch?v=kb-sUyJhoWw) - [WordPress Studio (WordPress.com local dev app)](https://developer.wordpress.com/studio/) - [Cursor](https://cursor.com) - [cursor.directory — WordPress rules](https://cursor.directory) - [WordPress Plugin Handbook — repository guidelines](https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/) ## 📝 Summary - What happened: Ferdy Korpershoek opens a three-part series by building two working WordPress plugins — a Jim Rohn quotes dashboard widget and a front/back-end time-tracking widget — using WordPress Studio for a local site and the free tier of Cursor for AI code generation, each from a single natural-language prompt. - Why it matters: the video is a clean specimen of the "vibe coding for WordPress" genre — it demonstrates real capability (one prompt, working plugin, deployed to a live site via zip upload) while glossing over review, security, and the gap between installing cursor.directory rules and actually meeting WordPress.org guidelines. - Key stakeholders: hobbyists and agency freelancers who want plugin-shaped products; the WordPress.org plugin review team, who will receive the downstream submissions; plugin-business incumbents whose moat this narrative erodes. - Risks and tradeoffs: "no coding knowledge required" removes the audience's ability to audit generated code; the time-tracker idea includes covertly tracking hired writers' time, a consent problem the video treats as a pro-version feature; "sell on autopilot" oversells the support and maintenance reality of commercial plugins. - Bottom line: the workflow (Studio + Cursor + guideline rules + one prompt) genuinely works for simple dashboard widgets and is a solid on-ramp; treat the business framing and the skipped code review as the part that needs adult supervision. ## 📖 Main Content - Core argument: AI collapses the barrier between "WordPress user" and "WordPress plugin creator." For years plugin development required experienced developers; now a single descriptive prompt in Cursor produces an installable plugin, so the constraint moves from coding skill to idea quality. - The stack, defined: **WordPress Studio** is WordPress.com's free local development app (Mac/Windows/Linux) that spins up a local WordPress site and — after both apps are installed — exposes an "open in Cursor" button. **Cursor** is the AI code editor; the whole tutorial runs on its free tier. **cursor.directory** hosts community rule sets; Ferdy installs three WordPress rule packs at the "home" scope so guidelines apply to every future project. - Workflow demonstrated: create empty local site in Studio → open the site folder in Cursor (manually linking the repo if the button doesn't) → install WordPress best-practice rules → prompt: "build a WordPress dashboard widget that shows a quote from Jim Rohn every time you refresh the page," pasting 20 quotes sourced from ChatGPT → plugin appears in `wp-content/plugins/` and works immediately, randomizing quotes per load. - Distribution without the repository: compress the plugin folder to a zip, upload via Plugins → Add New on any live site. That's the whole multi-site story for video one; repository submission is video two, pro-version monetization is video three. - Second demo raises the ceiling slightly: an untested one-prompt request for a dashboard widget tracking active time on the front end and back end — pitched as client-billing transparency — works on the first try, verified against a stopwatch. - Ideation method: plugins are born from your own repeated friction. Ferdy's example is his site-onboarding routine (delete default plugins/pages/posts, set display name, fix permalinks) which a plugin could reduce to one form submit across a thousand builds. - Contested claims to flag: "without knowing anything about coding" is true for producing code but false for evaluating it; installing cursor rules helps but does not guarantee passing WordPress.org review (sanitization, escaping, nonces, prefixing, GPL compliance still get human-reviewed); "sell it on autopilot" ignores support load, compatibility churn, and security responsibility; the suggestion to track contract writers' time without telling them is an ethics and, in some jurisdictions, a legal problem. ## 🗒️ Notes #### ⏱️ [00:00:00](https://www.youtube.com/watch?v=kb-sUyJhoWw&t=0) Hook and series roadmap - Premise: create a plugin with zero coding knowledge, submit it to the official repository, then sell a pro version "on autopilot." - Three videos: build and reuse (this one), publish to the WordPress.org repository, then productize a pro version. - Framing quote: "For years, only experienced web developers were able to create plugins. Now you can do it too, thanks to AI." #### ⏱️ [00:00:44](https://www.youtube.com/watch?v=kb-sUyJhoWw&t=44) Tooling setup: WordPress Studio plus Cursor - Downloads WordPress Studio from WordPress.com's developer page ("we're considering ourselves as developers these days") and Cursor's free tier; signs up with Google. - Creates an empty local site named "my WordPress website" in Studio. - After installing Cursor, restarting Studio surfaces a new "open in Cursor" button; if the repo doesn't auto-link, open the Studio site folder manually in Cursor. #### ⏱️ [00:03:59](https://www.youtube.com/watch?v=kb-sUyJhoWw&t=239) Guardrails: cursor.directory WordPress rules - Installs three WordPress rules/best-practices packs from cursor.directory, scoped to "home" so they apply to all future projects. - Rationale: repository submissions get rejected when they're out of line with WordPress guidelines; the rules keep Cursor pointed at them. - Rules are visible under Cursor settings → Rules, marked always applied. #### ⏱️ [00:05:11](https://www.youtube.com/watch?v=kb-sUyJhoWw&t=311) First plugin: Jim Rohn quotes dashboard widget - Prompt: build a dashboard widget showing a Jim Rohn quote on every refresh; 20 quotes generated by ChatGPT and pasted in; plugin named "Jim Rohn Quotes." - Cursor scaffolds the plugin into `wp-content/plugins/jim-rohn-quotes` almost instantly ("Wow. That went fast"). - Works on first activation; screen options used to hide other dashboard widgets; quotes randomize per refresh. #### ⏱️ [00:08:10](https://www.youtube.com/watch?v=kb-sUyJhoWw&t=490) Deploying to a live site by zip - Finder → wp-content/plugins → right-click → compress → upload the zip on the live site via Plugins → Add New → Upload Plugin. - Plugin activates and works identically on production; total tool spend so far: zero dollars. #### ⏱️ [00:09:32](https://www.youtube.com/watch?v=kb-sUyJhoWw&t=572) Business aside: products beat affiliate links - "You're an affiliate but the real money is where the products are" — advice Ferdy reports hearing from the WordPress community. - Software as a service is scalable and sellable in a way a face-driven YouTube channel is not. #### ⏱️ [00:10:15](https://www.youtube.com/watch?v=kb-sUyJhoWw&t=615) Second plugin: dashboard time tracker - Untested one-shot prompt: a dashboard widget counting active time spent on the front end and back end, pitched as honesty with clients about billed time. - Floated pro features: per-area breakdowns (editor, SEO) and tracking hired writers' time without mentioning it — the consent-free surveillance idea goes unexamined. - Verified with a stopwatch: roughly one minute back end, three minutes front end tracked correctly. #### ⏱️ [00:12:52](https://www.youtube.com/watch?v=kb-sUyJhoWw&t=772) Where plugin ideas come from - "Where do plugins get born? … They happen in your mind" — mine your own repeated tasks. - Example: his new-site onboarding checklist (remove default plugins/pages/posts, set name, fix permalinks) as a one-click onboarding plugin, saving a minute or two across a thousand sites. - Method: find where you get stuck building websites, solve it, package it, share it. #### ⏱️ [00:14:40](https://www.youtube.com/watch?v=kb-sUyJhoWw&t=880) Author metadata, exit thesis - One more prompt renames both plugins' author headers to "ferdy.com" — plugin metadata is just another thing Cursor edits. - Notes that popular plugins get acquired: build something helpful, and a company may buy it. - Closing thesis: "the combination of AI and WordPress is still one of the best combinations you can have." ## 📚 References - [WordPress Studio](https://developer.wordpress.com/studio/) — the local development app used throughout. - [Cursor](https://cursor.com) — AI editor; free tier used for both plugins. - [cursor.directory](https://cursor.directory) — source of the three WordPress rule packs. - [WordPress.org detailed plugin guidelines](https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/) — the actual bar video two must clear. - [Dashboard Widgets API](https://developer.wordpress.org/apis/dashboard-widgets/) — the API both demo plugins sit on. ## 🗣️ Paraphrase - You don't need to be a developer to ship a WordPress plugin anymore. Install WordPress Studio for a free local site, install Cursor, add community-maintained WordPress rules so the AI respects platform guidelines, then describe the plugin you want in one sentence. Ferdy does this twice — a motivational-quote dashboard widget and a time tracker — and both work on the first attempt. - Distribution is unglamorous and effective: zip the plugin folder and upload it to any live site. The bigger arc is economic — stop promoting other people's products as an affiliate and own a product, because software scales and sells in a way personal brands don't. The best plugin ideas are the tasks you already repeat every time you build a site. ## 📰 Newsletter - Ferdy Korpershoek just did the thing every WordPress freelancer has been quietly tempted to do: typed one sentence into Cursor and shipped a working dashboard plugin before his coffee cooled. Two, actually — a Jim Rohn quote widget and a billable-time tracker — on Cursor's free tier, with WordPress Studio as the local sandbox. - The underrated move in the video isn't the prompt, it's the prep: he installs the WordPress rules packs from cursor.directory *before* generating anything, so the AI at least aims at the plugin guidelines instead of inventing its own coding standards. Rules first, vibes second — a sentence the plugin review team would embroider on a pillow. - Fair warning between the lines: "no code knowledge needed" gets you to *generated*, not to *reviewed*. Before any of these zips touch a client site, someone who can read PHP should check the escaping, sanitization, and prefixing — the review queue rejects vibes. - Worth a click: [WordPress Studio](https://developer.wordpress.com/studio/), [cursor.directory](https://cursor.directory), and the [plugin guidelines](https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/) his video two will have to survive. ## ✅ Action Items #### DevRel - Developer advocacy: build a counterpart demo showing the same one-prompt plugin passing a real review checklist (escaping, sanitization, nonces, prefixes) — "vibe coded, review hardened" is a strong talk. - Education: workshop outline — Studio + AI editor + plugin guidelines rules as the beginner on-ramp, with a code-review literacy module bolted on. - Developer experience: compare cursor.directory WordPress rule packs against official handbook guidance; gaps are a docs contribution opportunity. - Developer marketing: this genre ("first plugin with AI") is pulling non-developers into the ecosystem — meet them with honest next-step content rather than ceding the narrative to monetization funnels. - Community management: expect a wave of AI-generated submissions; support content that sets review-queue expectations kindly. #### OSPO - License Compliance: AI-generated plugin code destined for WordPress.org must still be GPL-compatible; provenance of generated snippets is unaddressed in this genre. - Security Management: one-prompt plugins with no human audit are a supply-chain intake question for any org allowing them on production sites. - Developer Support: publish internal guardrails for "AI-built plugin on company sites" before someone uploads a zip. - Not applicable otherwise — the video has no inventory, policy, or funding surface. #### Community - Maintainers: repeated-friction ideation (Ferdy's onboarding-plugin example) is a good prompt for contributor idea clinics. - Contributors: AI-assisted first plugins could feed a "first submission" mentorship rotation pairing newcomers with reviewers. - Sponsors and Ecosystem: not applicable to this source — a solo tutorial with no funding or cross-project component. #### WordPress - Plugins: the review team is the pressure point for this whole content genre; throughput and automated pre-checks (Plugin Check) deserve amplification. - Training: Learn WordPress could own an honest version of this tutorial — same workflow, plus the security-review step the video skips. - Documentation: link the Dashboard Widgets API and plugin guidelines prominently from beginner AI-workflow content. - Marketing: "AI + WordPress is one of the best combinations" is a creator-community narrative worth channeling with accurate examples. - Core AI: one more data point that third-party editors (Cursor) are the current AI on-ramp; relevant to Core AI initiative scoping. - Other teams (Core, Mobile, Playground, Polyglots, etc.): not applicable to this source — a beginner tooling tutorial touching none of their surfaces. #### The WPCC - Not applicable to this source — no funding, fellowship, or governance angle in a solo plugin tutorial. ### FAIR - Not applicable to this source — distribution here is zip upload and the canonical .org repository; no federated/mirror concerns raised. ## 🧪 Hypotheses - One-prompt AI plugins succeed reliably only within well-trodden API surfaces (dashboard widgets, shortcodes) and fail at rates the genre never shows for anything involving data modeling or auth. - Installing WordPress rule packs in Cursor measurably reduces guideline violations in generated code versus no-rules generation, but does not bring pass rates near review-ready. - The WordPress.org plugin review queue sees a rising share of AI-generated first submissions during 2026, with rejection reasons clustering on sanitization/escaping and generic naming/prefixing. - Tutorial viewers who ship a first AI plugin are more likely to remain in the WordPress ecosystem (buy hosting, attend events) than viewers of theme-only content. - "Sell on autopilot" pro-version conversions for solo AI-built plugins are negligible without support infrastructure, contradicting the series' monetization arc. ### 📊 Methodology - Sample cursor.directory's WordPress rule packs; generate N standard plugin tasks with and without rules; score output against Plugin Check and manual review for escaping/sanitization/nonce/prefix violations. - Request or scrape aggregate WordPress.org review statistics (rejection categories over time) to test the AI-submission-wave hypothesis. - Replicate the two demo prompts across Cursor, Copilot, and Claude Code; compare first-try success and guideline compliance. - Survey plugin-review team members on observed AI-generation markers in submissions. ### ❓ Questions - Do the three cursor.directory rule packs conflict with each other or with current handbook guidance? - What does the generated time-tracker actually store, and does it disclose tracking to logged-in users — would it survive a privacy review? - How does WordPress.org's review team currently detect and handle AI-generated submissions with unaudited code? - Where is the capability cliff — the simplest prompt at which this workflow stops producing working plugins? ### 🔮 Future Research - A rubric for "review-ready" AI-generated plugin code that beginners can run without reading PHP (Plugin Check + automated static analysis as a pipeline). - Longitudinal tracking of videos two and three in this series: does the repository submission pass, and does the pro version sell? - Comparative study of Studio+Cursor vs wp-env+Claude Code vs Playground-based flows as beginner on-ramps. ### 💡 Implications - Practice: the constraint on plugin creation shifts from coding ability to idea selection and code-audit access; agencies can prototype internal tooling in minutes. - Policy: consent-free employee/contractor time tracking, casually suggested as a pro feature, collides with labor and privacy law; plugin directories may need clearer surveillance-feature policies. - Security: unaudited generated code deployed by authors who cannot read it is the exact preconditions for a new class of supply-chain incidents. - Education: curricula should teach code *evaluation* literacy before code *generation* workflows. - Funding models: the affiliate-to-product-owner migration narrative will push more creators into commercial plugin businesses, with support-load reality checks arriving later. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid roughly grade 5–6 on the transcript — short conversational sentences, minimal jargon. #### 👀 Visual learners - Present: continuous screen recording of every click, zoomed UI (CMD+ for visibility), live dashboard results. - Improve: an architecture-free workflow diagram (Studio → Cursor → rules → prompt → zip → live site) and file-tree callouts. #### 🔊 Aural learners - Present: full narration of every action with verbal signposting between steps. - Improve: a recap voiceover summarizing the five-step workflow at the end. #### 🗣️ Verbal learners - Present: plain-language framing, exact prompts read aloud, analogies (plugins "born in your mind"). - Improve: on-screen glossary for Studio, repository, pro version, and rules. #### 🧩 Kinesthetic learners - Present: the entire video is a follow-along lab with free tools and shortlinks. - Improve: a written step checklist and the two exact prompts in the description for replication. #### 🧠 Logical learners - Present: clear three-video sequence and a repeatable prompt → verify → deploy loop, including a stopwatch verification of the tracker. - Improve: a decision table for when one-prompt generation is sufficient versus when review is mandatory. #### 🧑‍🤝‍🧑 Social learners - Present: community anecdotes (affiliate advice), invitation to share plugins with the world. - Improve: prompt viewers to post their generated plugins for peer feedback. #### 🧘‍♀️ Solitary learners - Present: fully self-paced solo workflow requiring no collaboration. - Improve: reflection prompt — list your three most repeated site-build tasks as plugin candidates. #### 🌿 Naturalistic learners - Present: organic ideation metaphor — plugins grow from observed, recurring friction in your own environment. - Improve: lifecycle framing — what maintenance a plugin needs after it "grows up" (updates, compatibility, support). ### 📊 Accessibility Assessment #### Screen reader semantics - Present: assessment applies to the video artifact; YouTube auto-captions carry the narration. - Improve: the generated plugins' dashboard widgets should be checked for heading structure and accessible names — never mentioned in the video. #### Keyboard navigation - Present: not addressed; workflow is demonstrated entirely with mouse and trackpad. - Improve: note keyboard paths in wp-admin and verify the widgets introduce no focus traps. #### Contrast and readability - Present: zoomed UI (CMD+) explicitly for viewer readability. - Improve: verify generated widget text meets 4.5:1 in both admin color schemes. #### Text resizing and reflow - Not applicable to this source — no viewer-facing web content is authored beyond stock wp-admin widgets. #### Media and captions - Present: YouTube captioning available; visual steps are narrated, which aids non-sighted following. - Improve: publish a text transcript and step list; no audio descriptions exist. #### Forms and interactions - Not applicable to this source — the demo plugins render read-only widgets with no forms. #### Standards reference - Gaps map to WCAG 2.2 AA 1.1.1/1.2.x (media alternatives for the tutorial) and, for the generated plugins, 1.3.1 and 4.1.2 pending an audit the video never performs. ### 🌍 DEIB Assessment #### Cultural breadth - Present: cross-platform notes (Mac/Windows/Linux); a Dutch creator addressing a global audience; a "not in Africa, not in Asia… actually they are" aside acknowledges plugins are made everywhere. - Improve: quote sources are US male motivational speakers (Rohn, Robbins) plus scripture; broaden examples. #### Inclusive language - Present: consistently informal, jargon-light second-person address; non-native-speaker phrasing makes it approachable. - Improve: define repository, pro version, and permalinks on first use for true beginners. #### Neurodiversity support - Present: short sequential steps, one action per moment, visible results after each step. - Improve: chaptered timestamps and a written checklist would aid viewers who lose the thread in asides. #### Representation - Present: solo male creator; examples center his own brand (ferdy.com author attribution). - Improve: showcase community plugins from diverse authors as idea models. #### Psychological safety - Present: encouraging, failure-free tone ("I have not tested it" normalizes experimenting). - Improve: the covert-tracking pro-feature suggestion deserves an on-screen ethics caveat; none is given. ### ✅ Logical Validity #### Strong reasoning - Demonstration over assertion: both capability claims are proven live — the plugin appears in `wp-content/plugins/` and runs, and the tracker is validated against a stopwatch (11:50–13:51). That's sound inductive evidence for "this workflow builds simple widgets." - Means-end coherence: installing WordPress rules because non-compliant submissions "will be rejected" (04:49) correctly links tooling choice to a downstream gate. - Generalization from repetition: the ideation heuristic (repeated friction → plugin) is a valid abstraction from his onboarding example. #### Fallacies - Hasty generalization: two dashboard widgets → "you can create your own WordPress plugin without knowing anything about coding" (00:00). Fix: scope the claim to simple, well-documented API surfaces. - Appeal to wealth/anecdote: "the real money is where the products are" (09:43) rests on unnamed community anecdotes, and "sell it on autopilot" (00:12) omits support, maintenance, and security costs. Fix: present base rates for plugin-business success. - False assurance: rules installed ≈ guidelines met is implied; review still evaluates actual code. Fix: state that rules raise, not guarantee, compliance. - Suppressed consideration: recommending covert time tracking of hired writers (11:18) ignores consent entirely. Fix: name the disclosure requirement. #### Tone of voice - Enthusiastic, informal, self-deprecating infomercial-adjacent ("Oh man, I like it. I like it."; "You can make a tattoo of that."); confidence is affective rather than argumentative, closing on faith-inflected warmth ("God bless you"). ### 🛡️ DARVO Analysis - Not applicable to this source — a solo instructional video with no accusations, disputes, or adversarial framing to deny, attack, or reverse; the closest rhetorical move is gentle pushback on affiliate marketing, aimed at himself. ## 🎯 Conclusion - Bottom line: Studio + Cursor + community WordPress rules turns a one-sentence idea into a working dashboard plugin on a free stack, and Ferdy proves it twice on camera — but the video's "no coding knowledge" and "autopilot income" frames should be read as marketing, not method. - Next steps for readers: replicate the workflow on a local Studio site; run Plugin Check and a human review on anything AI-generated before it touches production; mine your own repeated tasks for plugin ideas; watch videos two and three critically, especially the repository-review outcome. ## 🔄 Refactor Appendix — Create Your First WordPress Plugin Using Cursor (Complete Tutorial) > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Defaults: 3 Literature, 1 Permanent. Resonance filter: if you can't > articulate in one line why a claim matters, drop it. > > Konik claim-header rules: present tense, declarative, ≤10 words when > possible, searchable, unique, mirrors annotation focus if present. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Atoms (H3) ### [H1] One prompt now yields a working WordPress plugin > [!quote] ID:rw_pending > So those are two very simple ideas, one prompt and two plugins. **Context & use**: - 13:58 — closing tally after both live demos succeed on first attempt. - Marks where the plugin-creation constraint moves from code skill to idea selection; core evidence for the vibe-coding-onramp thread. **Tags**: #xref **Highlight**: [view highlight](readwise://pending) <!-- atomicity: 1 idea ✓ --> ### [H2] Product ownership outearns affiliate promotion > [!quote] ID:rw_pending > You're an affiliate but the real money is where the products are. **Context & use**: - 09:43 — advice Ferdy reports receiving from the WordPress community, motivating the series' monetization arc. - The economic engine behind the whole "build plugins with AI" content genre; connects to creator-economy and plugin-business notes. **Tags**: #xref **Highlight**: [view highlight](readwise://pending) <!-- atomicity: 1 idea ✓ --> ### [H3] Repeated website friction generates plugin ideas > [!quote] ID:rw_pending > Where do you get stuck in creating websites? **Context & use**: - 13:32 — the ideation method, illustrated by his site-onboarding routine becoming a one-click plugin concept. - A reusable heuristic independent of AI tooling: audit your own repetition for product seeds. **Tags**: #xref #articleseed **Highlight**: [view highlight](readwise://pending) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### [P1] AI plugin generation shifts the bottleneck to code review **Claim** (one sentence, Courtney's voice): When AI makes plugin generation free, the scarce skill becomes evaluating generated code against platform guidelines, not writing it. **Evidence pointer**: [[#H1]] **Scope & conditions**: Holds for guideline-gated ecosystems like WordPress.org where human review is the shipping gate; weakens for private/internal tooling where nothing audits the output — which is exactly where the risk concentrates. **Links** (≥1 with annotation): - [[AI-assisted development workflows]] — because extends - [[WordPress plugin review process]] — because applies-in the submission pipeline - [[Vibe coding capability cliff]] — because contrasts on where generation reliability ends <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Compare cursor.directory's WordPress rule packs against the official plugin handbook — gap analysis could be a DevRel post — https://cursor.directory #fleeting #inbox - [F2] Watch video two of this series: does the AI-built plugin survive WordPress.org review? #fleeting #inbox ### → Things 3 (max 2 actions) - [ ] Replicate the one-prompt dashboard-widget flow in Studio and run Plugin Check on the output — vibe-coding on-ramp research #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Create Your First WordPress Plugin Using Cursor.md|Create Your First WordPress Plugin Using Cursor by Ferdy Korpershoek]] ## Highlights - idea. You're an affiliate but the real money is where the products are. So a lot of people want to ([View Highlight](https://read.readwise.io/read/01kxr9mgb9rrx6myabe4rj3e0d)) - Note: H2 — the economic motivation for the build-publish-monetize series: product ownership outearns affiliate promotion. - Tags: atom/literature/h2 - a minute or two minutes. So that's how ideas get born. Where do you get stuck in creating websites? ([View Highlight](https://read.readwise.io/read/01kxr9mjn3gzerpdgq4pwbnkq9)) - Note: H3 — the ideation heuristic: mine your own repeated site-build friction for plugin concepts. - Tags: atom/literature/h3 - depth. So those are two very simple ideas, one prompt and two plugins. So I mean, two times ([View Highlight](https://read.readwise.io/read/01kxr9mefdz8zj1t6cqq29m76a)) - Note: H1 — the closing tally: one prompt each, two working dashboard-widget plugins on Cursor's free tier, first attempt. - Tags: atom/literature/h1