diff --git a/.codex-plugin/plugin.json b/.codex-plugin/plugin.json index c10b580..5a723a6 100644 --- a/.codex-plugin/plugin.json +++ b/.codex-plugin/plugin.json @@ -1,7 +1,7 @@ { "name": "opencode-power-pack", "version": "0.3.0", - "description": "Eleven Claude Code workflows packaged for Codex, OpenCode, and Pi.", + "description": "Twelve Claude Code workflows packaged for Codex, OpenCode, and Pi.", "author": { "name": "Wayner Barrios", "url": "https://github.com/waybarrios" @@ -24,7 +24,7 @@ "skills": "./skills/", "interface": { "displayName": "OpenCode + Codex Power Pack", - "shortDescription": "Eleven workflows for Codex, OpenCode, and Pi", + "shortDescription": "Twelve workflows for Codex, OpenCode, and Pi", "longDescription": "Review code, audit security, design and implement features, build MCP servers, and maintain project guidance with reusable workflows for Codex, OpenCode, and Pi.", "developerName": "Wayner Barrios", "category": "Productivity", diff --git a/LICENSES/Omp-designer-MIT.txt b/LICENSES/Omp-designer-MIT.txt new file mode 100644 index 0000000..f6394e8 --- /dev/null +++ b/LICENSES/Omp-designer-MIT.txt @@ -0,0 +1,26 @@ +MIT License + +Copyright (c) 2026 Leandro (LePro10) + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. + +SPDX-License-Identifier: MIT +Declared in package.json ("license": "MIT") of https://github.com/LePro10/omp-designer +at commit fc8abdc0d2046b64c2d442a361948b5c53f2e16f; no separate LICENSE file +is published upstream. diff --git a/README.md b/README.md index 2377f45..59b3f55 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@

OpenCode Power Pack for Codex, OpenCode + Pi

- Eleven Claude Code workflows, adapted for Codex, OpenCode, and Pi.
+ Twelve Claude Code workflows, adapted for Codex, OpenCode, and Pi.
Code review, security audit, feature development, frontend design, project memory, and authoring tools.

@@ -14,7 +14,7 @@ GitHub stars Last commit GitHub issues - Skills: 11 + Skills: 12 OpenCode 1.18.7+ Codex plugin Pi package @@ -45,7 +45,7 @@ Start a new Codex session, open `/plugins` to confirm the installation, or invok pi install git:github.com/waybarrios/opencode-power-pack ``` -Pi discovers the eleven skills declared by the package. Use `pi list` to verify the installation. For a project-local installation recorded in `.pi/settings.json`, add `-l`: +Pi discovers the twelve skills declared by the package. Use `pi list` to verify the installation. For a project-local installation recorded in `.pi/settings.json`, add `-l`: ```bash pi install git:github.com/waybarrios/opencode-power-pack -l @@ -55,7 +55,7 @@ pi install git:github.com/waybarrios/opencode-power-pack -l Codex, OpenCode, and Pi read `SKILL.md` workflows, but many valuable Claude Code workflows originated as Claude-specific commands and agents. Copying those artifacts directly does not preserve their orchestration, permissions, or subagent behavior. -This package adapts the portable methodology into shared skills, registers feature-development specialist roles as read-only OpenCode subagents, lets Codex execute the same phase assignments with its native subagent workflow, and exposes all eleven skills as a Pi package. It ships immutable provenance for every upstream work. +This package adapts the portable methodology into shared skills, registers feature-development specialist roles as read-only OpenCode subagents, lets Codex execute the same phase assignments with its native subagent workflow, and exposes all twelve skills as a Pi package. It ships immutable provenance for every upstream work. It complements [obra/superpowers](https://github.com/obra/superpowers), which provides process skills such as brainstorming, TDD, debugging, and plan execution. @@ -70,6 +70,7 @@ It complements [obra/superpowers](https://github.com/obra/superpowers), which pr | Feature development | `code-architect` | Produce a file-level architecture and implementation blueprint | | Feature development | `code-reviewer` | Adversarial review of a focused local change set | | Design | `frontend-design` | Create distinctive interfaces with an accessibility and craft rubric | +| Design | `ai-slop` | Rubric to judge whether a design is generic "AI slop" or genuinely product-fit | | Authoring | `mcp-builder` | Design and build MCP servers in TypeScript or Python | | Authoring | `skill-creator` | Create, test, and improve reusable `SKILL.md` workflows | | Project memory | `agents-md-improver` | Audit project rules and propose targeted improvements | @@ -97,7 +98,7 @@ codex plugin add opencode-power-pack@opencode-power-pack codex plugin list --marketplace opencode-power-pack ``` -Start a new Codex session after installation so the eleven bundled skills are loaded. Use `/plugins` to inspect the installed plugin or `$` to select one of its skills explicitly. Codex plugin packaging follows the [official plugin structure](https://developers.openai.com/plugins/build/plugins). +Start a new Codex session after installation so the twelve bundled skills are loaded. Use `/plugins` to inspect the installed plugin or `$` to select one of its skills explicitly. Codex plugin packaging follows the [official plugin structure](https://developers.openai.com/plugins/build/plugins). ### OpenCode From GitHub @@ -137,7 +138,7 @@ opencode debug skill opencode debug agent code-explorer ``` -The first command should include all eleven unprefixed skill names. The second should report a `subagent` with editing denied. In the TUI, `ctrl+p` should list `/code-review`, `/feature-dev`, `/frontend-design`, and the other skill-derived commands. +The first command should include all twelve unprefixed skill names. The second should report a `subagent` with editing denied. In the TUI, `ctrl+p` should list `/code-review`, `/feature-dev`, `/frontend-design`, and the other skill-derived commands. ### Verify Codex diff --git a/THIRD_PARTY_NOTICES.md b/THIRD_PARTY_NOTICES.md index 34d1201..627f698 100644 --- a/THIRD_PARTY_NOTICES.md +++ b/THIRD_PARTY_NOTICES.md @@ -9,6 +9,15 @@ The skills are modified derivatives of the sources recorded in records the immutable upstream commit, source path, Git blob, license, and adaptation type reviewed for this distribution. +## OMP Designer + +The modified `ai-slop` skill derives from the MIT-licensed `LePro10/omp-designer` +repository (`skills/ai-slop.md`, condensed from ~740 to under 500 lines for the +skill-body length limit; core rubric, tests, and severity model preserved). + +Copyright 2026 Leandro (LePro10). The upstream notice is available at +`LICENSES/Omp-designer-MIT.txt`. + ## Anthropic Official Plugins The following modified skills derive from Apache-2.0 material in diff --git a/UPSTREAMS.json b/UPSTREAMS.json index 21661ac..a4e3360 100644 --- a/UPSTREAMS.json +++ b/UPSTREAMS.json @@ -42,6 +42,19 @@ "blob": "b7f201db19ec485271945e350914e6ac5a8957bd" } }, + { + "name": "ai-slop", + "license": "MIT", + "adaptation": "adapted", + "reviewedAt": "2026-08-02", + "source": { + "repository": "https://github.com/LePro10/omp-designer", + "commit": "fc8abdc0d2046b64c2d442a361948b5c53f2e16f", + "committedAt": "2026-07-02T18:33:40+02:00", + "path": "skills/ai-slop.md", + "blob": "bf81402b348bdd158ae3aa9f1c29d07939db2fd3" + } + }, { "name": "code-architect", "license": "Apache-2.0", diff --git a/package.json b/package.json index eb55977..aa581d7 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "opencode-power-pack", "version": "0.3.0", - "description": "Eleven Claude Code workflows packaged for Codex, OpenCode, and Pi: code review, feature development, security review, frontend design, authoring, and project memory.", + "description": "Twelve Claude Code workflows packaged for Codex, OpenCode, and Pi: code review, feature development, security review, frontend design, authoring, and project memory.", "type": "module", "main": ".opencode/plugins/opencode-power-pack.js", "engines": { diff --git a/skills/ai-slop/SKILL.md b/skills/ai-slop/SKILL.md new file mode 100644 index 0000000..a32dc88 --- /dev/null +++ b/skills/ai-slop/SKILL.md @@ -0,0 +1,104 @@ +--- +name: ai-slop +description: Operational rubric that turns "don't make AI slop" into observable properties, severity levels, evidence requirements, and repair actions for interface design. Use as the reference rubric when building or reviewing marketing sites, product interfaces, dashboards, portfolios, or e-commerce pages, especially alongside frontend-design. +license: MIT (modified; see UPSTREAMS.json) +--- + +Scope: marketing sites, product interfaces, dashboards, portfolios, editorial pages, and e-commerce. Complements `frontend-design`: that skill builds the interface, this one is the detailed rubric for judging whether the result is generic ("AI slop") or genuinely fit for the product. + +This is not a universal style guide. It does not ban a visual style merely because AI systems use it often — a gradient, card grid, serif headline, glass surface, or dark theme may be appropriate. It becomes a slop signal when used by reflex rather than because the product, audience, content, interaction, or brand requires it. + +MUST/MUST NOT are required for acceptance; SHOULD/SHOULD NOT are default rules whose deviations need a written rationale; MAY is optional and context-dependent. + +## 1. Core definition + +**AI slop is superficially competent output that lacks sufficient intention, grounding, specificity, coherence, truthfulness, or product fit.** It usually shows up as one or more of: + +1. **Default-driven** — recognizable model/template reflexes replace deliberate decisions. +2. **Interchangeable** — could be relabeled for another product with minimal change. +3. **Ungrounded** — content, claims, visuals, or features aren't supported by the brief or evidence. +4. **Incoherent** — polished elements that don't form one consistent system. +5. **Decorative without purpose** — effects attract attention without clarifying hierarchy, meaning, state, or action. +6. **Quantity-over-value** — extra sections/cards/copy exist mainly to look complete. +7. **Unreviewed** — obvious responsive, accessibility, factual, or interaction defects remain. +8. **Overfitted to current AI aesthetics** — follows the fashionable model output distribution rather than the project's needs. + +Output is **not** slop merely because AI helped produce it — a result can be AI-assisted and still strong when it's grounded in real product/user context, deliberately art-directed, specific, factually honest, coherent, accessible, edited, browser-validated, and hard to transplant unchanged to another product. Human-made work can also be slop; the classification concerns the output, not proof of authorship. + +## 2. Two quick tests + +- **Substitution test**: could the product name, logo, and accent color be swapped while 80% of the page stays equally plausible for another product? Yes = strong slop risk; No = likely meaningfully tied to the product. +- **Rationale test**: every prominent decision MUST answer at least one of: what user need does this serve, what product truth does it express, what hierarchy does it clarify, what brand trait does it embody, what interaction state does it communicate, what constraint made it appropriate? If the only answer is "it looks modern" or "AI suggested it," it's a slop candidate. + +## 3. Evaluation dimensions (score each 0-4: 0 excellent, 1 minor, 2 noticeable, 3 serious, 4 blocking) + +- **Product grounding & specificity** — generic value props, checklist-driven sections, invented features/personas, visual metaphors unrelated to the product. *Evidence:* a `PRODUCT.md` (or equivalent) with explicit users, jobs, constraints, and a traceable reason per section. *Repair:* cut unsupported sections, rewrite around concrete user tasks. +- **Truthfulness & evidence** (blocking) — invented prices, metrics, testimonials, logos, citations, or controls that imply unavailable functionality. Use `[NEEDS INPUT]`, "Price on request," or clearly labeled sample data instead; keep an evidence ledger for verifiable claims; mark fictional demo data as demo data. +- **Information architecture & narrative** — default hero → logo cloud → cards → metrics → testimonials → pricing → FAQ; shuffleable section order; front-loaded slogans. *Repair:* define the reader's questions in order, give each section a unique job, cut sections that don't advance understanding. +- **Composition & layout** — everything centered, identical repeated cards, uniform spacing, excessive pills, desktop merely stacked on mobile, heading overflow at mid widths. *Repair:* content-led layouts, intentional density variation, a spatial system broken only for a reason, test real content at multiple widths. +- **Visual system coherence** — inconsistent radii/shadows/icon weights, unrelated surface treatments per section, tokens defined but bypassed. *Evidence:* a `DESIGN.md` with semantic tokens (color, type, spacing, radius, elevation, motion) that components actually consume, and a documented exception when something breaks the system. +- **Color & material** — unexplained purple/violet "tech" gradients, cyan glows on dark backgrounds, gradient headline text without purpose, glassmorphism everywhere, palette chosen from category stereotype alone. None of these are automatically forbidden — flag them when repeated, unsupported by the brand concept, or chosen as a reflex. +- **Typography** — same popular default typefaces everywhere, one weight pattern for every role, oversized display type for "editorial" feel, tiny tracked eyebrow labels, flat hierarchy, hero text that fails on mobile. *Repair:* select type from brand attributes and reading conditions, define role-based type tokens, test long words/localization/zoom. +- **Copy & voice** — "revolutionize/unlock/seamless/elevate," "not just X, but Y," empty claims ("built for the future"), repetitive cadence and em dashes, "Learn more" buttons with a predictable destination. *Repair:* concrete nouns/verbs, state what the product does for whom and why, remove undemonstrable claims. +- **Imagery & iconography** — generic gradient blobs standing in for the product, unlicensed stock hotlinks, AI imagery with anatomy/lighting inconsistencies, mixed icon families. *Repair:* authentic product imagery, purpose-built illustration, real screenshots, or honest placeholders — define an art-direction rule before generating assets. +- **Motion & interaction** — every element fades/rises on scroll, indiscriminate bounce easing, long entrance sequences, parallax with no semantic purpose, motion that ignores reduced-motion preferences. *Repair:* write a motion rationale, use a small tokenized duration/easing system, test keyboard/touch/reduced-motion/low-performance conditions. +- **Usability & accessibility** (blocking signals) — keyboard traps, missing focus states, insufficient contrast, unlabeled controls, tiny targets, hover-only information, broken zoom/reflow. Baseline: WCAG 2.2 AA for ordinary public-facing work. +- **Responsive behavior** — desktop grid collapsed into an undifferentiated stack, horizontal overflow, abrupt type-scale jumps, unchanged content priority on small screens. *Repair:* pick breakpoints from content failure (not device labels), test narrow/medium/wide plus zoom. +- **Functional completeness** — dead buttons/links, forms that can't submit or report state, tabs/menus/dialogs implemented only visually, missing loading/empty/error/disabled states. *Repair:* browser-based task tests from the brief, including edge states; never present incomplete controls as finished. +- **Implementation quality** — avoidable layout shift, unoptimized assets, excessive client JS for static content, repeated one-off CSS values, invalid semantics, console/hydration errors, performance sacrificed for decoration. +- **Distinctiveness & category reflex** — could someone guess the palette/typography/hero/components from the category alone (first-order reflex)? After banning the obvious cliché, did the result just move to the next fashionable alternative, e.g. dark-purple-glass → cream-editorial-serif (second-order reflex)? A design should feel plausible for *this* project, not inevitable from its category. + +## 4. Cross-signal rule and severity + +Classify the result as slop when: one **blocking** issue exists, three or more dimensions score 3, the same reflex repeats across multiple registers (color + typography + layout + copy), or both quick tests fail. + +- **Blocking** (must fix before delivery): fabricated claims/facts, broken primary tasks, serious accessibility failures, deceptive controls, unusable responsive behavior, missing evidence for public claims, legal/safety-risk content. +- **Major** (strongly harms quality/distinctiveness): page-wide template reflex, incoherent design system, repetitive composition, unreadable typography, purposeless motion, generic copy dominating the experience. +- **Minor** (localized): one unnecessary pill, one weak label, one inconsistent radius, one overly long line, one generic section. + +## 5. Required project artifacts + +- **`PRODUCT.md`**: product/offer, target users, primary jobs, key tasks, real facts vs. assumptions, non-goals, content gaps, accessibility target, success criteria. +- **`DESIGN.md`**: art-direction sentence, brand attributes, anti-references, extracted principles from visual references, palette and semantic color roles, typography roles, spacing/grid system, radius/border/elevation/material rules, imagery direction, motion rules, component vocabulary, responsive principles, intentional exceptions. +- **`EVIDENCE.md`**: for every externally verifiable claim — exact claim, source, confidence, allowed wording, where it appears. Unsupported claims MUST NOT ship. + +## 6. Review pipeline + +A single self-review is insufficient. Gate through, in order: + +1. **Deterministic source scan** — unsupported numbers/claims, forbidden phrase patterns, off-token colors/spacing, typography violations, inaccessible semantics, small targets, missing states, broken links, console/perf defects. +2. **Browser task tests** — keyboard navigation, forms/validation, menus/dialogs, error/empty states, mobile navigation, reduced motion, realistic content lengths. +3. **Screenshot review** — narrow mobile, wide mobile/small tablet, laptop, wide desktop, 200% zoom where relevant; inspect hierarchy, rhythm, overflow, coherence, product fit. +4. **Visual judge** — a vision-capable evaluator scores dimension-by-dimension against this rubric and the brief, with evidence tied to visible regions and a confidence level; "AI-looking" is not automatically low quality. +5. **Pairwise comparison** — candidate vs. previous version, vs. a control build without this rubric, vs. one alternative art direction, or vs. a relevant reference. Prefer pairwise preference over isolated "8/10" scores. +6. **Human acceptance** — does this feel made for this product? What feels generic, dishonest, or unsupported? What would be remembered tomorrow? Which decision would a competent designer challenge? + +## 7. Scoring + +Track two separate results — never collapse them into one number: + +- **Shipping readiness** (pass/fail): blocking defects, functional tasks, accessibility target, evidence. A visually distinctive page can still fail shipping readiness. +- **Slop risk** (weighted 0-100): product grounding 15, truthfulness 15, information architecture 10, composition/layout 10, system coherence 10, copy/voice 8, typography 7, color/material 7, imagery 5, motion 5, responsive 4, distinctiveness 4. 0-14 low risk, 15-29 minor concerns, 30-49 noticeable genericity, 50-69 major slop characteristics, 70-100 dominated by slop. + +## 8. Repair protocol + +When slop is detected: name the failed dimension, cite visible/source-level evidence, identify whether the cause is missing context, a model reflex, incomplete implementation, or weak review, remove unsupported content before adding polish, fix the system or rule (not just the symptom), re-run the deterministic/browser/screenshot checks, compare pairwise against the previous version, and record what changed and why. + +## 9. Anti-overcorrection + +Do not turn "anti-slop" into another recognizable house style. Don't automatically replace dark-neon with cream-editorial, sans-serif with giant italic serif, cards with arbitrary asymmetry, gradients with flat beige, polished copy with forced quirkiness, or standard layouts with scroll gimmicks. The goal isn't to look less like one AI default by adopting another — it's decisions justified by the project. + +## 10. Stable principles vs. temporal trends + +Separate rules into two layers so the rubric doesn't fight yesterday's cliché while ignoring tomorrow's: + +- **Stable (no expiry)**: interchangeability/substitution, product grounding, truthfulness, coherence, accessibility, functional completeness, rationale, distinctiveness-from-stereotype. +- **Temporal (contextual, must expire)**: give each an introduction date and a review date, e.g. `dark-purple-cyan-glass-default` (current LLM tech-product default — flag when used without brand rationale) or `overused-default-fonts: Inter, Roboto, Geist, Plus Jakarta Sans, Space Grotesk` (exception: Roboto Mono for monospace, Roboto Condensed for display). Review temporal rules at their review date; drop them if the trend faded, otherwise renew. A temporal rule MUST NOT become a new predictable default — after banning a trend, check whether the agent just adopted the next fashionable alternative instead. + +## 11. Definition of done + +No blocking issue remains; primary tasks work in the browser; claims are supported or explicitly labeled; the accessibility target is met; screenshots pass responsive review; the design is internally coherent; prominent decisions have written rationale; the substitution test doesn't reveal broad interchangeability; pairwise review prefers the final result over its control/previous version; remaining known limitations are documented. + +## 12. Compact instruction (use under tight context) + +AI slop is superficially polished but insufficiently intentional, grounded, specific, coherent, truthful, or product-fit output. Don't judge styles in isolation — detect default reflexes, interchangeability, unsupported content, system inconsistency, decorative excess, incomplete interaction, and unreviewed defects. Ground every major decision in `PRODUCT.md`/`DESIGN.md`, verify claims through `EVIDENCE.md`, test real browser tasks and responsive screenshots, and use pairwise review instead of a self-assigned score. A common visual treatment is fine when deliberate, coherent, accessible, and justified by the project. diff --git a/tests/codex-plugin.test.mjs b/tests/codex-plugin.test.mjs index 90f5272..64876f1 100644 --- a/tests/codex-plugin.test.mjs +++ b/tests/codex-plugin.test.mjs @@ -24,7 +24,7 @@ test("Codex plugin exposes every bundled skill with valid basic frontmatter", () const names = readdirSync(join(REPO, "skills")) .filter((name) => existsSync(join(REPO, "skills", name, "SKILL.md"))); - assert.equal(names.length, 11); + assert.equal(names.length, 12); for (const name of names) { const source = readFileSync(join(REPO, "skills", name, "SKILL.md"), "utf8"); assert.match(source, /^---\r?\n/); diff --git a/tests/pi-package.test.mjs b/tests/pi-package.test.mjs index bace11e..b9545cc 100644 --- a/tests/pi-package.test.mjs +++ b/tests/pi-package.test.mjs @@ -13,10 +13,10 @@ test("Pi package declares the bundled skills directory", () => { assert.match(packageJson.description, /Pi/); }); -test("Pi package exposes all eleven SKILL.md workflows", () => { +test("Pi package exposes all twelve SKILL.md workflows", () => { const skillRoot = join(REPO, packageJson.pi.skills[0]); const skills = readdirSync(skillRoot) .filter((name) => existsSync(join(skillRoot, name, "SKILL.md"))); - assert.equal(skills.length, 11); + assert.equal(skills.length, 12); });