Add elite-frontend-design-2026 and bugbuster skills#10
Add elite-frontend-design-2026 and bugbuster skills#10AcerThyRacer wants to merge 1 commit intoLeonxlnx:mainfrom
Conversation
- elite-frontend-design-2026: A complete rework of the taste skill with modern April 2026 platform capabilities, expanded framework coverage (React 19, Svelte 5, Vue 3.5+, Astro 5, SwiftUI, Jetpack Compose, etc.), deterministic design dials, dependency verification protocol, and comprehensive pre-flight check matrix. - bugbuster: A new forensic bug-detection skill for finding bugs across codebases. Covers concurrency, security, resource lifecycle, state machines, supply chain, and modern AI/agentic-system failure modes.
📝 WalkthroughWalkthroughTwo new skill specification documents are introduced: BugBuster defines standardized bug-finding review directives with compliance rules, heuristics, and a forensic investigation architecture; Elite Polyglot Frontend Design 2026 establishes frontend design standards across multiple ecosystems with configurable design dials, platform-specific guidelines, and pre-flight checklists. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~28 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Reviewer's GuideAdds two new skills to the codebase: an Sequence diagram for bugbuster skill analyzing a pull requestsequenceDiagram
actor User
participant Assistant
participant BugBusterSkill
participant Repo as Repository
User->>Assistant: Submit PR for bug review
Assistant->>BugBusterSkill: Initialize with baseline dials
BugBusterSkill->>BugBusterSkill: Apply user overrides to dials
BugBusterSkill->>Repo: Fetch diff and referenced files
Repo-->>BugBusterSkill: Return diff and file contents
BugBusterSkill->>BugBusterSkill: Verify files and line numbers exist
BugBusterSkill->>BugBusterSkill: Run language and framework heuristics
BugBusterSkill->>BugBusterSkill: Apply bug hunting directives
BugBusterSkill->>BugBusterSkill: Run AI agent specific checks
BugBusterSkill->>BugBusterSkill: Construct findings with severity and confidence
BugBusterSkill->>BugBusterSkill: Run pre-flight review checks
BugBusterSkill-->>Assistant: Structured bug report for PR
Assistant-->>User: Present ranked findings and minimal fix suggestions
Class diagram for elite-frontend-design-2026 skill structureclassDiagram
class EliteFrontendDesign2026Skill {
+string name
+string description
+int DESIGN_VARIANCE
+int MOTION_INTENSITY
+int VISUAL_DENSITY
+selectStack(userContext)
+applyDialOverrides(userPrompt)
+generateUIArtifacts(requirements)
+runPreFlightChecks(artifact)
}
class DialConfiguration {
+int DESIGN_VARIANCE
+int MOTION_INTENSITY
+int VISUAL_DENSITY
+setBaselineValues()
+adjustForPromptKeywords(keywords)
+mapAmbiguousBriefToDials(briefType)
}
class FrameworkMatrix {
+selectWebStack(projectSignals)
+selectMobileStack(projectSignals)
+selectDesktopStack(projectSignals)
+selectWasmStack(projectSignals)
}
class StackHeuristics {
+detectFromFiles(files)
+detectFromConfig(configFiles)
+inferDefaultForWeb()
}
class StylingStandards {
+applyTailwindV4Rules(projectTailwindVersion)
+applyVanillaCSSCapabilities()
+applyTypedStylingAlternatives(choice)
}
class DesignDirectives {
+enforceTypographyRules()
+enforceColorCalibration()
+enforceLayoutPatterns()
+enforceInteractiveStates()
}
class MotionSystem {
+selectMotionLibrary(stack)
+configureMotionFromDials(DESIGN_VARIANCE, MOTION_INTENSITY, VISUAL_DENSITY)
+enforceGPUOnlyAnimations()
}
class AccessibilityGuardrails {
+enforceWCAG22AA()
+applyPlatformSpecificA11y(stack)
}
class PerformanceGuardrails {
+enforceWebPerfTargets()
+enforceMobilePerfTargets()
}
class DependencyVerificationProtocol {
+verifyManifestForImport(manifest, dependency)
+emitInstallCommandIfMissing(dependency, packageManager)
+verifyTailwindVersionSyntax(manifest)
+verifyRuntimeEnvironmentVersions()
}
class PreFlightCheckMatrix {
+runArchitectureChecks(artifact)
+runStylingChecks(artifact)
+runLayoutChecks(artifact)
+runInteractivityChecks(artifact)
+runMotionChecks(artifact)
+runAccessibilityChecks(artifact)
+runPerformanceChecks(artifact)
+runContentChecks(artifact)
+runDependencyChecks(artifact)
+runPlatformSpecificChecks(artifact)
}
EliteFrontendDesign2026Skill --> DialConfiguration : uses
EliteFrontendDesign2026Skill --> FrameworkMatrix : uses
FrameworkMatrix --> StackHeuristics : uses
EliteFrontendDesign2026Skill --> StylingStandards : enforces
EliteFrontendDesign2026Skill --> DesignDirectives : enforces
EliteFrontendDesign2026Skill --> MotionSystem : configures
EliteFrontendDesign2026Skill --> AccessibilityGuardrails : enforces
EliteFrontendDesign2026Skill --> PerformanceGuardrails : enforces
EliteFrontendDesign2026Skill --> DependencyVerificationProtocol : enforces
EliteFrontendDesign2026Skill --> PreFlightCheckMatrix : validatesWith
MotionSystem --> DialConfiguration : reads
DesignDirectives --> DialConfiguration : reads
Class diagram for bugbuster skill structureclassDiagram
class BugBusterSkill {
+string name
+string description
+int SUSPICION_LEVEL
+int ANALYSIS_DEPTH
+int BLAST_RADIUS
+analyzeDiff(diff)
+analyzeRepository(repoScope)
+generateFindings()
+rankAndLabelFindings()
}
class BugBusterDials {
+int SUSPICION_LEVEL
+int ANALYSIS_DEPTH
+int BLAST_RADIUS
+setBaselineValues()
+applyUserOverrides(request)
+validateDialInteraction()
}
class Methodology {
+verifyRepoFilesBeforeClaims()
+enforceReproductionOrTrace()
+labelConfidenceForFinding()
+calibrateSeverity()
+verifyDependenciesBeforeAPIClaims()
+enforceNoFabrication()
}
class LanguageHeuristics {
+analyzeTypeScriptJavaScript(file)
+analyzePython(file)
+analyzeRust(file)
+analyzeGo(file)
+analyzeKotlinJava(file)
+analyzeSwift(file)
}
class FrameworkHeuristics {
+analyzeReactNext(component)
+analyzeDjangoFastAPI(handler)
+analyzeVueSvelte(component)
+analyzeAndroidCompose(component)
}
class BugHuntingDirectives {
+applyDeterministicTraceAnalysis()
+analyzeConcurrencyPatterns()
+analyzeTrustBoundaries()
+analyzeResourceLifecycles()
+analyzeFailureStates()
+analyzeDataAndSchemaPatterns()
+analyzeIdempotency()
+analyzeObservability()
+analyzeMigrationsAndRollouts()
}
class CreativeProactivity {
+detectPromptInjectionViaToolOutput()
+detectContextWindowTruncation()
+detectMCPHandshakeTOCTOU()
+detectStreamingReaderLeaks()
+detectToolCallLoops()
+detectHierarchicalMemoryStaleness()
+detectSupplyChainShifts()
}
class AnalysisGuardrails {
+preventSpeculativeCVEs()
+enforceProofBeforeAlarm()
+enforceOneBugPerFinding()
+separateDiffVsPreExistingFindings()
+requireExplicitAssumptions()
+orderFindingsBySeverity()
}
class ReportStructureEngine {
+buildFindingTitle()
+attachSeverityAndConfidence()
+attachLocationAndTrigger()
+describeImpactAndMechanism()
+attachProposedFix()
+attachRegressionRisk()
+attachTestVector()
+groupFindingsBySeverity()
+summarizeCrossCuttingThemes()
+recordOutOfScopeAreas()
+recordUnknownsLedger()
}
class RootCauseForensicsEngine {
+collectEvidence()
+generateDifferentialDiagnosis()
+applyBranchingFiveWhy()
+classifyDefectArchetype()
+proposeMinimalFixes()
+analyzeRegressionRisk()
+designTestVectors()
+planBisection()
+triangulateWithLogsAndTelemetry()
+designReproductionStrategy()
}
class PreFlightReviewCheck {
+verifyLineNumbers()
+verifyLabelsForFindings()
+verifyCriticalFindingsHaveRepro()
+verifyDiffFocus()
+verifyNoHallucinatedArtifacts()
+verifyAgentSpecificDefectsReviewed()
+verifyUnknownsLedger()
}
BugBusterSkill --> BugBusterDials : configuresWith
BugBusterSkill --> Methodology : enforces
BugBusterSkill --> LanguageHeuristics : uses
BugBusterSkill --> FrameworkHeuristics : uses
BugBusterSkill --> BugHuntingDirectives : applies
BugBusterSkill --> CreativeProactivity : applies
BugBusterSkill --> AnalysisGuardrails : enforces
BugBusterSkill --> ReportStructureEngine : formatsWith
BugBusterSkill --> RootCauseForensicsEngine : uses
BugBusterSkill --> PreFlightReviewCheck : validatesWith
BugHuntingDirectives --> BugBusterDials : reads
CreativeProactivity --> BugBusterDials : reads
AnalysisGuardrails --> BugBusterDials : reads
Flow diagram for bugbuster forensic review processgraph TD
A["Start review request"] --> B["Load BugBusterSkill with baseline dials"]
B --> C["Apply user overrides to SUSPICION_LEVEL, ANALYSIS_DEPTH, BLAST_RADIUS"]
C --> D["Verify repository files and manifests are available"]
D --> E["Scope analysis to diff or requested files"]
E --> F["Run language and framework heuristics on scoped code"]
F --> G["Apply bug hunting directives
(trace, concurrency, boundaries, lifecycle)"]
G --> H["Apply creative proactivity checks
(agent and AI-specific defects)"]
H --> I["Aggregate raw issues"]
I --> J["For each issue: reproduce or construct invariant-violating trace"]
J --> K["Label each finding with severity and confidence"]
K --> L["Build structured findings using report template"]
L --> M["Run pre-flight review check
(no fabrication, proper ordering, diff focus)"]
M --> N["Output triage-ready bug report"]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've found 1 issue, and left some high level feedback:
- Both skills define their own dependency verification rules; consider extracting a shared, referenced section for manifest/version checks so that future updates to the protocol don’t diverge between
elite-frontend-design-2026andbugbuster. - The
elite-frontend-design-2026skill hardcodes many specific version floors and feature assumptions (e.g., Tailwind v4, React 19, container queries baseline availability); it may be worth briefly stating how the assistant should behave when the detected project stack predates those capabilities to avoid conflicting guidance.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Both skills define their own dependency verification rules; consider extracting a shared, referenced section for manifest/version checks so that future updates to the protocol don’t diverge between `elite-frontend-design-2026` and `bugbuster`.
- The `elite-frontend-design-2026` skill hardcodes many specific version floors and feature assumptions (e.g., Tailwind v4, React 19, container queries baseline availability); it may be worth briefly stating how the assistant should behave when the detected project stack predates those capabilities to avoid conflicting guidance.
## Individual Comments
### Comment 1
<location path="skills/elite-frontend-design-2026/SKILL.md" line_range="451" />
<code_context>
+- Oversaturated accents (`#ff00ff`, `#00ffff`).
+- Text-fill gradients on large headers ("text-transparent bg-clip-text bg-gradient-to-r from-purple-500 to-pink-500").
+- Custom mouse cursors.
+- Skeumorphic "glow behind card" effects.
+- Default Tailwind colors used verbatim (`bg-blue-500`, `text-gray-700`) in premium contexts — customize via the `@theme` block.
+
</code_context>
<issue_to_address>
**suggestion (typo):** Minor spelling correction: "Skeuomorphic" instead of "Skeumorphic".
Please update this bullet to use the correct spelling: `Skeuomorphic "glow behind card" effects.`
```suggestion
- Skeuomorphic "glow behind card" effects.
```
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
| - Oversaturated accents (`#ff00ff`, `#00ffff`). | ||
| - Text-fill gradients on large headers ("text-transparent bg-clip-text bg-gradient-to-r from-purple-500 to-pink-500"). | ||
| - Custom mouse cursors. | ||
| - Skeumorphic "glow behind card" effects. |
There was a problem hiding this comment.
suggestion (typo): Minor spelling correction: "Skeuomorphic" instead of "Skeumorphic".
Please update this bullet to use the correct spelling: Skeuomorphic "glow behind card" effects.
| - Skeumorphic "glow behind card" effects. | |
| - Skeuomorphic "glow behind card" effects. |
There was a problem hiding this comment.
Pull request overview
This PR adds two new instruction “skills” under skills/ to expand the repo’s guidance library: one for premium cross-framework frontend design in April 2026, and one for high-rigor forensic bug detection.
Changes:
- Added
elite-frontend-design-2026skill with framework matrix, modern CSS/motion/a11y rules, and a pre-flight checklist. - Added
bugbusterskill with dial-driven methodology, confidence/severity labeling requirements, and advanced failure-mode hunting patterns.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| skills/elite-frontend-design-2026/SKILL.md | Introduces a new “elite” frontend design skill with multi-stack standards and comprehensive guardrails. |
| skills/bugbuster/SKILL.md | Introduces a new bug-hunting skill emphasizing evidence, labeling, and layered analysis patterns. |
| --- | ||
| name: elite-frontend-design-2026 | ||
| description: Senior polyglot UI/UX engineer that architects premium interfaces across all modern frontend stacks — React 19, Next.js 15+, Svelte 5, Vue 3.5+, SolidJS, Astro 5, Qwik 2, SwiftUI, Jetpack Compose, React Native New Architecture, Flutter, Tauri v2, and Rust WASM (Leptos/Dioxus). Enforces April 2026 platform capabilities (container queries, anchor positioning, view transitions, scroll-driven animations, OKLCH color, Tailwind v4 CSS-first config, React 19 Actions, Svelte 5 runes, Vue Vapor Mode). Overrides LLM cliché biases with metric-driven dials, strict component architecture, GPU-only animation paths, WCAG 2.2 AA accessibility gates, and a dependency-verification protocol. Trigger for any UI, component, page, dashboard, mobile screen, or design-engineering task in any language. | ||
| license: MIT |
There was a problem hiding this comment.
This new skill directory isn't referenced in the repo’s skill indexes (e.g., skill.sh, README.md skills table, and skills/llms.txt). If those are the canonical discovery/registry points, add an entry for elite-frontend-design-2026 so users can find/use it via the documented flows.
| --- | ||
| name: bugbuster | ||
| description: Senior Principal Engineer specializing in forensic bug detection across codebases. Overrides default LLM biases toward shallow syntactic review. Enforces layered analysis covering concurrency, security, resource lifecycle, state machines, supply chain, and modern AI/agentic-system failure modes calibrated to April 2026 standards. | ||
| --- |
There was a problem hiding this comment.
bugbuster is added under skills/, but it’s not listed in the repo’s skill indexes (skill.sh, README.md skills table, skills/llms.txt). If those lists are used for discovery/registry, add bugbuster there so it’s reachable via the standard install/usage paths.
| --- | ||
| name: elite-frontend-design-2026 | ||
| description: Senior polyglot UI/UX engineer that architects premium interfaces across all modern frontend stacks — React 19, Next.js 15+, Svelte 5, Vue 3.5+, SolidJS, Astro 5, Qwik 2, SwiftUI, Jetpack Compose, React Native New Architecture, Flutter, Tauri v2, and Rust WASM (Leptos/Dioxus). Enforces April 2026 platform capabilities (container queries, anchor positioning, view transitions, scroll-driven animations, OKLCH color, Tailwind v4 CSS-first config, React 19 Actions, Svelte 5 runes, Vue Vapor Mode). Overrides LLM cliché biases with metric-driven dials, strict component architecture, GPU-only animation paths, WCAG 2.2 AA accessibility gates, and a dependency-verification protocol. Trigger for any UI, component, page, dashboard, mobile screen, or design-engineering task in any language. | ||
| license: MIT |
There was a problem hiding this comment.
license: MIT is the only extra YAML front-matter key used across skills; other SKILL.md files only include name and description. If the skills loader expects a fixed schema, this extra key may be ignored or could break parsing—consider removing it or adding license metadata consistently across all skills after confirming tool compatibility.
| license: MIT |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 14a4a485f7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| @@ -0,0 +1,445 @@ | |||
| --- | |||
| name: bugbuster | |||
There was a problem hiding this comment.
Adding this skill file (and the paired elite-frontend-design-2026 file) without updating skill.sh and skills/llms.txt leaves both new skills undiscoverable through the repo’s own registry workflow: bash skill.sh bugbuster / bash skill.sh elite-frontend-design-2026 currently return empty output because neither name is in the SKILLS map, and the skills index file is stale as well. Please add both entries wherever the repository enumerates available skills.
Useful? React with 👍 / 👎.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (6)
skills/bugbuster/SKILL.md (2)
213-213: Verify JavaScriptfor...inprototype pollution interaction.Line 213 states "
for...inOver Array: Iterates enumerable keys, including prototype pollution additions." Whilefor...indoes iterate enumerable properties including those on the prototype chain, calling this a direct "prototype pollution" issue may be slightly imprecise. The issue is thatfor...initerates inherited enumerable properties, which becomes a problem if prototype pollution has occurred elsewhere. Consider clarifying that this is a consequence of prototype pollution rather than the pollution itself.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/bugbuster/SKILL.md` at line 213, Update the phrasing for the "`for...in` Over Array" entry so it clarifies that `for...in` itself iterates enumerable properties (including inherited ones) and that iterating inherited properties becomes a problem only if prototype pollution has occurred elsewhere; replace the current assertion that it "includes prototype pollution additions" with a note like "iterates inherited enumerable properties — which can expose prototype-polluted properties if prototype pollution has occurred."
223-223: Clarify Python datetime comparison behavior.Line 223 states "Comparisons with aware datetimes raise." This is imprecise—comparing naive and aware datetimes raises a
TypeError, but this isn't about "raising" in general. Consider rephrasing to: "Comparisons with aware datetimes raiseTypeError" for technical precision.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/bugbuster/SKILL.md` at line 223, Update the phrasing that follows the bullet "* **`datetime.utcnow()` Naive:** Comparisons with aware datetimes raise." to explicitly state the exception type: change it to something like "Comparisons between naive and aware datetimes raise a TypeError; use datetime.now(timezone.utc) for aware datetimes." Target the bullet that contains "`datetime.utcnow()` Naive" and replace the imprecise wording with the clarified sentence mentioning `TypeError`.skills/elite-frontend-design-2026/SKILL.md (4)
567-572: Add language identifier to grid composition code block.The grid composition example would benefit from a language identifier. Consider using
plaintextortextfor this layout diagram.📝 Proposed fix
-``` +```plaintext Row 1: grid-cols-3 → card-wide (col-span-2) | card-square Row 2: grid-cols-3 → card-square | card-wide (col-span-2) Row 3: grid-cols-2 → card-tall | card-tall</details> As per coding guidelines from static analysis, fenced code blocks should have a language specified. <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@skills/elite-frontend-design-2026/SKILL.mdaround lines 567 - 572, Locate
the fenced code block that contains the grid composition diagram (the lines
starting "Row 1: grid-cols-3 → card-wide (col-span-2) | card-square", "Row 2:
grid-cols-3 → card-square | card-wide (col-span-2)", and "Row 3: grid-cols-2
→ card-tall | card-tall") and add a language identifier to the opening fence
(for example changetoplaintext or ```text) so the fenced block includes
the language specifier.</details> --- `25-29`: **Add language identifier to fenced code block.** The code block defining the dials would benefit from a language identifier for better syntax highlighting and tooling support. Consider adding `plaintext` or `yaml` as the language identifier. <details> <summary>📝 Proposed fix</summary> ```diff -``` +```plaintext DESIGN_VARIANCE: 8 (1 = perfect symmetry → 10 = artsy chaos) MOTION_INTENSITY: 6 (1 = fully static → 10 = cinematic physics) VISUAL_DENSITY: 4 (1 = art gallery → 10 = Bloomberg terminal) ``` ``` </details> As per coding guidelines from static analysis, fenced code blocks should have a language specified. <details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against the current code and only fix it if needed.
In
@skills/elite-frontend-design-2026/SKILL.mdaround lines 25 - 29, The fenced
code block containing the dial definitions (DESIGN_VARIANCE, MOTION_INTENSITY,
VISUAL_DENSITY) lacks a language identifier; update the opening triple-backtick
to include a language such as plaintext or yaml (e.g., ```plaintext) so the
block is properly highlighted and complies with the static-analysis guideline
for fenced code blocks.</details> --- `145-145`: **Clarify availability of iOS 19-specific features.** The reference to "Liquid Glass / Material 2026" features "introduced for iOS 19" may be premature for an April 2026 document, as iOS 19 would typically be in beta at this time. Consider either removing iOS 19-specific features or clearly marking them as beta/preview with appropriate caveats about their availability. <details> <summary>🤖 Prompt for AI Agents</summary> ``` Verify each finding against the current code and only fix it if needed. In `@skills/elite-frontend-design-2026/SKILL.md` at line 145, The line mentioning ".glassEffect()" and ".regularMaterial" uses an iOS 19-specific API; update the text to either remove the iOS 19 claim or explicitly mark ".glassEffect()" as beta/preview for iOS 19 (with a short caveat about limited availability and instability) and keep ".regularMaterial" as the documented fallback for older targets, so readers know to use ".regularMaterial" when ".glassEffect()" isn't available. ``` </details> --- `234-251`: **Consider adding browser compatibility caveats for baseline features.** While the document confidently states these CSS features are "Baseline-available in April 2026," some features like anchor positioning and `@starting-style` may have varying levels of browser support. Consider adding brief notes about any remaining compatibility considerations or graceful degradation strategies, especially for features that were recently standardized. <details> <summary>🤖 Prompt for AI Agents</summary> ``` Verify each finding against the current code and only fix it if needed. In `@skills/elite-frontend-design-2026/SKILL.md` around lines 234 - 251, Add concise browser-compatibility caveats to the "7.2 Vanilla CSS (2026 capabilities)" section: for each potentially inconsistent feature (reference `anchor-name` / `position-anchor`, `@starting-style`, Popover API attributes `popover`/`popovertarget`, View Transitions `document.startViewTransition()` and `@view-transition`, scroll-driven `animation-timeline`, and `:has()`), append a short parenthetical note like "(check browser support)" or a one-sentence fallback strategy; include a single footnote or sentence pointing to authoritative support trackers (MDN / Can I Use), and suggest graceful-degradation patterns (feature-detect with CSS/JS, fallback to `position: absolute`/JS positioning, use IntersectionObserver if `animation-timeline` unsupported, and avoid reliance on `@starting-style` where unsupported). ``` </details> </blockquote></details> </blockquote></details> <details> <summary>🤖 Prompt for all review comments with AI agents</summary>Verify each finding against the current code and only fix it if needed.
Inline comments:
In@skills/elite-frontend-design-2026/SKILL.md:
- Line 54: Update the SwiftUI table row that currently reads "SwiftUI (iOS 18+ /
iOS 19) | Swift 6, iOS 18" by removing the incorrect "iOS 19" reference and
replacing it with the correct current version (e.g., "iOS 26" or "iOS 26+" for
forward compatibility); ensure the row reads consistently (for example: "SwiftUI
(iOS 18+ / iOS 26)" or "SwiftUI (iOS 18+ / iOS 26+)") and keep the rest of the
cell ("Swift 6, iOS 18" and the description) unchanged.- Line 357: Update the inaccurate package note by changing the phrase "motion
(formerlyframer-motion)" to indicate both packages coexist; e.g., say
"motion(recommended) orframer-motion" or add a short parenthetical that
motionis the newer entry point whileframer-motionremains maintained;
modify the text that currently mentions "motion" and "framer-motion" so it
reflects this coexistence and recommendation.- Line 111: Update the Vue Vapor Mode version requirement text to reference the
correct minimum Vue release: change the mention of "Vue 3.5+" to "Vue 3.6+" in
the paragraph that begins "Vue Vapor Mode:" so it accurately reflects that
Vapor Mode was introduced in Vue 3.6.0 (alpha) and remains in beta; keep the
rest of the note about trade-offs intact.- Around line 217-232: Update the phrasing about Tailwind v4 config files:
replace "no longer used" with "no longer required" and add a brief note that
tailwind.config.{js,ts}can still be loaded via the@configdirective for
advanced scenarios; refer to thetailwind.config.{js,ts}symbol and the
@configdirective so readers know where to find/enable legacy config support
while keeping the CSS-first guidance (@theme,@utility) intact.
Nitpick comments:
In@skills/bugbuster/SKILL.md:
- Line 213: Update the phrasing for the "
for...inOver Array" entry so it
clarifies thatfor...initself iterates enumerable properties (including
inherited ones) and that iterating inherited properties becomes a problem only
if prototype pollution has occurred elsewhere; replace the current assertion
that it "includes prototype pollution additions" with a note like "iterates
inherited enumerable properties — which can expose prototype-polluted properties
if prototype pollution has occurred."- Line 223: Update the phrasing that follows the bullet "*
datetime.utcnow()
Naive: Comparisons with aware datetimes raise." to explicitly state the
exception type: change it to something like "Comparisons between naive and aware
datetimes raise a TypeError; use datetime.now(timezone.utc) for aware
datetimes." Target the bullet that contains "datetime.utcnow()Naive" and
replace the imprecise wording with the clarified sentence mentioning
TypeError.In
@skills/elite-frontend-design-2026/SKILL.md:
- Around line 567-572: Locate the fenced code block that contains the grid
composition diagram (the lines starting "Row 1: grid-cols-3 → card-wide
(col-span-2) | card-square", "Row 2: grid-cols-3 → card-square | card-wide
(col-span-2)", and "Row 3: grid-cols-2 → card-tall | card-tall") and add a
language identifier to the opening fence (for example changetoplaintext
or ```text) so the fenced block includes the language specifier.- Around line 25-29: The fenced code block containing the dial definitions
(DESIGN_VARIANCE, MOTION_INTENSITY, VISUAL_DENSITY) lacks a language identifier;
update the opening triple-backtick to include a language such as plaintext or
yaml (e.g., ```plaintext) so the block is properly highlighted and complies with
the static-analysis guideline for fenced code blocks.- Line 145: The line mentioning ".glassEffect()" and ".regularMaterial" uses an
iOS 19-specific API; update the text to either remove the iOS 19 claim or
explicitly mark ".glassEffect()" as beta/preview for iOS 19 (with a short caveat
about limited availability and instability) and keep ".regularMaterial" as the
documented fallback for older targets, so readers know to use ".regularMaterial"
when ".glassEffect()" isn't available.- Around line 234-251: Add concise browser-compatibility caveats to the "7.2
Vanilla CSS (2026 capabilities)" section: for each potentially inconsistent
feature (referenceanchor-name/position-anchor,@starting-style, Popover
API attributespopover/popovertarget, View Transitions
document.startViewTransition()and@view-transition, scroll-driven
animation-timeline, and:has()), append a short parenthetical note like
"(check browser support)" or a one-sentence fallback strategy; include a single
footnote or sentence pointing to authoritative support trackers (MDN / Can I
Use), and suggest graceful-degradation patterns (feature-detect with CSS/JS,
fallback toposition: absolute/JS positioning, use IntersectionObserver if
animation-timelineunsupported, and avoid reliance on@starting-stylewhere
unsupported).</details> <details> <summary>🪄 Autofix (Beta)</summary> Fix all unresolved CodeRabbit comments on this PR: - [ ] <!-- {"checkboxId": "4b0d0e0a-96d7-4f10-b296-3a18ea78f0b9"} --> Push a commit to this branch (recommended) - [ ] <!-- {"checkboxId": "ff5b1114-7d8c-49e6-8ac1-43f82af23a33"} --> Create a new PR with the fixes </details> --- <details> <summary>ℹ️ Review info</summary> <details> <summary>⚙️ Run configuration</summary> **Configuration used**: defaults **Review profile**: CHILL **Plan**: Pro **Run ID**: `435d12d7-a58d-45b6-b82f-e581cef19783` </details> <details> <summary>📥 Commits</summary> Reviewing files that changed from the base of the PR and between d3696fbabe59898448c7ee22bcacc912e0f9c3cd and 14a4a485f7f574446cdb074d92f2dbe2ca6d300a. </details> <details> <summary>📒 Files selected for processing (2)</summary> * `skills/bugbuster/SKILL.md` * `skills/elite-frontend-design-2026/SKILL.md` </details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
| | A | Astro 5 | Astro 5.0 | Content-heavy sites, marketing, blogs, docs — Server Islands by default. | | ||
| | A | SolidJS 1.9+ / SolidStart | Solid 1.9 | Ultra-fast reactivity without VDOM; great for real-time UIs. | | ||
| | B | Qwik 2 + Qwik City | Qwik 2.0 | Resumability; instant-load marketing pages. | | ||
| | S | SwiftUI (iOS 18+ / iOS 19) | Swift 6, iOS 18 | Apple platforms; use Observation framework and `@Observable`. | |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
When is iOS 19 expected to be released? What is the typical iOS release schedule?
💡 Result:
iOS 19 was skipped; Apple rebranded to year-based versioning starting with iOS 26, released on September 15, 2025. There is no iOS 19 release. The next version, iOS 27, is expected to be announced at WWDC on June 8, 2026, with developer beta that day, public beta in July 2026, and public release around mid-September 2026 (likely September 14). Apple's typical iOS release schedule is: announcement at WWDC in early June, developer betas starting immediately after, public betas in July, and stable public release in mid-September alongside new iPhones. Historical examples: iOS 26 (Sep 15, 2025), iOS 18 (Sep 16, 2024), iOS 17 (Sep 18, 2023).
Citations:
- 1: https://www.macrumors.com/2025/05/28/apple-ios-26/
- 2: https://www.youtube.com/watch?v=C1AGi3KDlSI
- 3: https://en.wikipedia.org/wiki/IOS_version_history
- 4: https://9to5mac.com/2026/04/07/ios-27-release-date-when-next-major-iphone-update-is-coming/
- 5: https://9to5mac.com/2026/01/16/ios-27-new-features/
- 6: https://9to5mac.com/2026/03/23/apple-announces-wwdc-2026-for-june-8-ios-27-set-to-be-revealed
Remove the iOS 19 reference from the SwiftUI row.
iOS 19 does not exist. Apple switched to year-based versioning; as of April 2026, iOS 26 is current, with iOS 27 expected in September 2026. The row should reference only iOS 26, or iOS 26+ if forward-compatibility is intended.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/elite-frontend-design-2026/SKILL.md` at line 54, Update the SwiftUI
table row that currently reads "SwiftUI (iOS 18+ / iOS 19) | Swift 6, iOS 18" by
removing the incorrect "iOS 19" reference and replacing it with the correct
current version (e.g., "iOS 26" or "iOS 26+" for forward compatibility); ensure
the row reads consistently (for example: "SwiftUI (iOS 18+ / iOS 26)" or
"SwiftUI (iOS 18+ / iOS 26+)") and keep the rest of the cell ("Swift 6, iOS 18"
and the description) unchanged.
| - **`<script setup>` is mandatory.** No Options API in new code. | ||
| - **`defineModel()`** replaces manual `v-model` prop/emit pairs. | ||
| - **Reactive props destructuring** is stable — destructure `const { foo } = defineProps<{...}>()` and it stays reactive. | ||
| - **Vue Vapor Mode:** for performance-critical islands, opt in to Vapor Mode (no VDOM, compile-to-direct-DOM). Mention the trade-off: smaller, faster, but smaller ecosystem support. |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
What is Vue Vapor Mode and is it available in Vue 3.5?
💡 Result:
Vue Vapor Mode is an opt-in compilation mode for Vue Single-File Components (SFCs) that skips the Virtual DOM at runtime. The compiler generates direct DOM-update code using Vue's reactive system, resulting in smaller bundle sizes (e.g., 65% reduction in Hello World app), lower memory usage (42% less), and faster updates (up to 66% faster in list diffing benchmarks). It supports Composition API with <script setup vapor> and a subset of features (no Options API, limited SSR/Transitions/KeepAlive in early versions). Vapor components can mix with VDOM via vaporInteropPlugin or createVaporApp for pure Vapor apps. It is not available in Vue 3.5, which focuses on reactivity optimizations, reactive props destructure, SSR improvements, and other features without Vapor Mode mentions. Vapor Mode was merged via PR #12359 into the minor branch and first appeared in Vue 3.6.0-alpha.1 (July 2025), with betas continuing into March 2026 (e.g., 3.6.0-beta.9). As of 2026-04-18, Vue 3.5 remains the stable release (up to 3.5.32), while 3.6 is in beta/prerelease.
Citations:
- 1: https://medium.com/@sampan090611/vue-3-6-vapor-mode-opening-virtual-dom-era-dfd10023cd05
- 2: Vapor mode vuejs/core#12359
- 3: https://github.com/vuejs/core/releases/tag/v3.6.0-alpha.1
- 4: https://blog.vuejs.org/posts/vue-3-5
- 5: vuejs/core@589691c
- 6: https://github.com/vuejs/core/releases/tag/v3.6.0-beta.8
- 7: https://github.com/vuejs/core/releases/tag/v3.6.0-beta.9
- 8: vuejs/core@7fa1a53
Correct Vue version requirement for Vapor Mode.
Vue Vapor Mode is not available in Vue 3.5—it was first released in Vue 3.6.0-alpha.1 (July 2025) and remains in beta as of April 2026. Update the document to reference "Vue 3.6+" instead of "Vue 3.5+" when discussing Vapor Mode.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/elite-frontend-design-2026/SKILL.md` at line 111, Update the Vue Vapor
Mode version requirement text to reference the correct minimum Vue release:
change the mention of "Vue 3.5+" to "Vue 3.6+" in the paragraph that begins
"**Vue Vapor Mode:**" so it accurately reflects that Vapor Mode was introduced
in Vue 3.6.0 (alpha) and remains in beta; keep the rest of the note about
trade-offs intact.
| - **CSS-first config.** The `tailwind.config.{js,ts}` file is no longer used. Configuration lives in CSS via `@theme` and `@utility`: | ||
| ```css | ||
| @import "tailwindcss"; | ||
| @theme { | ||
| --color-accent: oklch(68% 0.19 145); | ||
| --font-display: "Geist", sans-serif; | ||
| --radius-card: 2rem; | ||
| } | ||
| ``` | ||
| - **PostCSS plugin:** use `@tailwindcss/postcss` — **never** `tailwindcss` as a PostCSS plugin (that was v3 syntax and breaks v4 builds). | ||
| - **Vite plugin** (`@tailwindcss/vite`) is the fastest path for Vite projects. | ||
| - **No `content` array.** v4 auto-detects. | ||
| - **Container queries are first-class:** `@container` utilities (`@lg:grid-cols-3`) work out of the box. | ||
| - **Dynamic utilities:** `w-[72rem]`, `text-[13px]`, `grid-cols-[1fr_auto_1fr]` — use them; they compile. | ||
| - **CSS variables are real CSS variables.** Every theme token is exposed as `--color-accent`, `--font-display`, etc. Use them directly in arbitrary values: `bg-[--color-accent]`. | ||
| - **Version detection:** inspect `package.json`. If `tailwindcss@^3`, do not emit v4 syntax. If `tailwindcss@^4`, do not emit `tailwind.config.ts` edits. |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
What is the configuration system for Tailwind CSS v4? Does it use CSS-first @theme blocks?
💡 Result:
Tailwind CSS v4 uses a CSS-first configuration system with @theme blocks, replacing the traditional JavaScript tailwind.config.js file. Customizations like design tokens (colors, fonts, breakpoints) are defined directly in CSS using the @theme directive after importing Tailwind. Example: @import "tailwindcss"; @theme { --font-display: "Satoshi", "sans-serif"; --breakpoint-3xl: 1920px; --color-avocado-500: oklch(0.84 0.18 117.33); } This generates corresponding utility classes (e.g., font-display, 3xl:, bg-avocado-500) and exposes values as CSS variables on :root. Legacy JS configs can still be loaded via @config if needed, but CSS-first is the primary approach with zero-config by default for content detection.
Citations:
- 1: https://tailwindcss.com/blog/tailwindcss-v4
- 2: https://bryananthonio.com/blog/configuring-tailwind-css-v4/
- 3: https://v3.tailwindcss.com/docs/v4-beta
- 4: https://tailwindcss.com/docs/configuration
🌐 Web query:
Tailwind CSS v4 PostCSS plugin setup and configuration @tailwindcss/postcss``
💡 Result:
To set up and configure the Tailwind CSS v4 PostCSS plugin (@tailwindcss/postcss): 1. Install the required packages: npm install tailwindcss @tailwindcss/postcss postcss 2. Configure your postcss.config.mjs (or postcss.config.js): export default { plugins: { "@tailwindcss/postcss": {}, } } Note: Remove 'postcss-import' and 'autoprefixer' if previously used, as they are handled automatically in v4. 3. In your main CSS file (e.g., src/input.css), import Tailwind: @import "tailwindcss"; 4. Run your build process (e.g., npm run dev). For manual setups, use PostCSS CLI: npx postcss src/input.css -o dist/output.css --watch 5. Link the output CSS in your HTML and start using Tailwind classes. Key changes from v3: The PostCSS plugin is now in a separate @tailwindcss/postcss package (not tailwindcss directly). Use @import instead of @tailwind directives. Configuration is CSS-first with @theme (optional, zero-config by default). Content paths in tailwind.config.js if needed for custom scanning.
Citations:
- 1: https://tailwindcss.com/docs/installation/using-postcss
- 2: https://tailwindcss.com/docs/upgrade-guide
- 3: https://tailwindcss.com/blog/tailwindcss-v4
🌐 Web query:
Tailwind CSS v4 Vite plugin @tailwindcss/vite setup
💡 Result:
To set up Tailwind CSS v4 with the @tailwindcss/vite plugin in a Vite project: 1. Create a new Vite project (if needed): npm create vite@latest my-project cd my-project 2. Install the packages: npm install tailwindcss @tailwindcss/vite 3. Configure the Vite plugin in vite.config.ts (or vite.config.js): import { defineConfig } from 'vite' import tailwindcss from '@tailwindcss/vite' export default defineConfig({ plugins: [tailwindcss], }) 4. Add to your main CSS file (e.g., src/style.css or src/index.css): @import "tailwindcss"; 5. Ensure the CSS is imported in your HTML or entry point (e.g., or via JS import). 6. Run the dev server: npm run dev Start using Tailwind classes in your HTML/JSX/TSX files. No tailwind.config.js or content configuration is needed; v4 auto-detects content. This uses the official first-party Vite plugin for optimal performance, replacing the old PostCSS setup.
Citations:
- 1: https://tailwindcss.com/docs/v4-beta
- 2: https://dev.to/goldenekpendu/how-to-install-tailwind-v4-in-a-vite-project-g3d
- 3: https://tailwindcss.com/docs/installation/using-vite
- 4: https://tailwindcss.com/docs
- 5: https://tailwindcss.com/docs/installation
- 6: https://tailwindcss.com/blog/tailwindcss-v4
🌐 Web query:
Tailwind CSS v4 container queries and dynamic utility classes
💡 Result:
Tailwind CSS v4 introduces native support for container queries and enhanced dynamic utility capabilities. Container Queries: - Mark a parent element with the @container class to establish a query container. - Use @sm, @md, etc., prefixes on child utilities for min-width queries (mobile-first, applies at target size and above). - Use @max-sm, @max-md for max-width queries. - Combine for ranges, e.g., @sm:@max-lg:flex-row. - Default breakpoints: @3xs (16rem) to @7xl (80rem). - Customize via --container-* CSS variables in @theme. - Supports container query units like cqw (container query width), e.g., w-[50cqw]. - No plugin needed; built-in since v4.0 alpha (released Jan 2025). Dynamic Utility Classes: - Many utilities now accept arbitrary numbers without config, e.g., grid-cols-15, px-7.5 (derived from --spacing scale). - Spacing utilities (px-, mt-, w-, etc.) dynamically compute from --spacing CSS var. - Arbitrary values enhanced: [value] syntax generates on-demand; supports CSS vars like fill-[var(--my-color)], or shorthand fill-(--my-brand-color). - Functional utilities via @utility in CSS: e.g., @utility tab- { tab-size: --value(--tab-size-*); } for tab-4, tab-[8]. - Supports theme values, bare values (inherit), arbitrary ([length]), modifiers (/50). - Custom utilities with addUtilities/matchUtilities APIs available (v3-like, limited). - Runtime dynamic classes (e.g., bg-${color} from API) don't work due to build-time compilation; use safelist, inline styles, or CSS vars for truly dynamic needs. - Arbitrary properties: [clip-path:circle(50%)]. Examples: Container:
Citations:
- 1: https://tailwindcss.com/blog/tailwindcss-v4
- 2: https://tailwindcss.com/docs/responsive-design
- 3: https://tailwindcss.com/docs/adding-custom-styles
- 4: https://cixel.com.au/blog/tailwind-css-v4-functional-utilities
Clarify the status of Tailwind v4 config files—they are optional, not deprecated.
The document correctly describes Tailwind v4's CSS-first architecture: the @theme block, @tailwindcss/postcss PostCSS plugin, and @tailwindcss/vite Vite plugin are all accurately presented. Container queries, dynamic utilities, and CSS variable exposure are confirmed features.
One clarification: tailwind.config.{js,ts} files are no longer required (zero-config by default), but they can still be loaded via the @config directive if needed for advanced scenarios. Rephrase to "no longer required" rather than "no longer used" for precision.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/elite-frontend-design-2026/SKILL.md` around lines 217 - 232, Update
the phrasing about Tailwind v4 config files: replace "no longer used" with "no
longer required" and add a brief note that `tailwind.config.{js,ts}` can still
be loaded via the `@config` directive for advanced scenarios; refer to the
`tailwind.config.{js,ts}` symbol and the `@config` directive so readers know
where to find/enable legacy config support while keeping the CSS-first guidance
(`@theme`, `@utility`) intact.
|
|
||
| ### 10.1 Library selection | ||
|
|
||
| - **Web (React):** `motion` (formerly `framer-motion`) for component animations; `gsap` for complex scroll-telling; `three` + `@react-three/fiber` for 3D. |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Has framer-motion been renamed to motion package on npm?
💡 Result:
No, framer-motion has not been renamed to a package simply called "motion" on npm. Framer Motion has become independent from Framer and is now branded as "Motion", but the primary npm package remains "framer-motion", actively maintained with version 12.38.0 as of March 2026, hosted at github.com/motiondivision/motion. A separate "motion" package exists (also version 12.38.0), but it depends on "framer-motion" and serves as an alternative entry point. Official upgrade instructions recommend uninstalling framer-motion and installing "motion", then changing imports to "motion/react". However, the framer-motion package continues to receive updates, points to motion.dev, and explicitly states "Framer Motion is now Motion". Both packages are published by the same author (Matt Perry), share the same repository, and have high download counts (framer-motion: 39.6M weekly; motion: 10.7M weekly). Existing code using framer-motion continues to work without changes.
Citations:
- 1: https://motion.dev/magazine/framer-motion-is-now-independent-introducing-motion
- 2: https://motion.dev/docs/react-upgrade-guide
- 3: https://www.npmjs.com/package/framer-motion
- 4: https://www.npmjs.com/package/motion
Correct the framer-motion package reference. The statement "motion (formerly framer-motion)" is inaccurate. Framer Motion has not been renamed; instead, a new motion package exists as the recommended alternative entry point, while framer-motion remains actively maintained. Update to: "motion (recommended) or framer-motion" or provide context that explains both packages coexist with motion being the newer approach.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/elite-frontend-design-2026/SKILL.md` at line 357, Update the
inaccurate package note by changing the phrase "motion (formerly
`framer-motion`)" to indicate both packages coexist; e.g., say "`motion`
(recommended) or `framer-motion`" or add a short parenthetical that `motion` is
the newer entry point while `framer-motion` remains maintained; modify the text
that currently mentions "motion" and "framer-motion" so it reflects this
coexistence and recommendation.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 2 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="skills/bugbuster/SKILL.md">
<violation number="1" location="skills/bugbuster/SKILL.md:149">
P2: Conflicting policy text gives opposite instructions on dependency/supply-chain findings, causing inconsistent reviewer behavior.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| * **NO "Missing Error Handling" Without a Caller:** Unhandled throw is fine if the caller is a framework boundary that renders a 500. Confirm the caller before flagging. | ||
| * **NO Regex Paranoia:** Not every regex is ReDoS. Flag only when (a) user-controllable input reaches the pattern and (b) the pattern has nested quantifiers or ambiguous alternation. | ||
| * **NO "Weak Cryptography" Blanket Claims:** MD5 is fine for file-dedupe checksums. Flag only in authentication, integrity, password, or signature contexts. | ||
| * **NO Dependabot Replay:** If the user has not requested a dependency audit, do not produce one. Those findings belong in a separate tool. |
There was a problem hiding this comment.
P2: Conflicting policy text gives opposite instructions on dependency/supply-chain findings, causing inconsistent reviewer behavior.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At skills/bugbuster/SKILL.md, line 149:
<comment>Conflicting policy text gives opposite instructions on dependency/supply-chain findings, causing inconsistent reviewer behavior.</comment>
<file context>
@@ -0,0 +1,445 @@
+* **NO "Missing Error Handling" Without a Caller:** Unhandled throw is fine if the caller is a framework boundary that renders a 500. Confirm the caller before flagging.
+* **NO Regex Paranoia:** Not every regex is ReDoS. Flag only when (a) user-controllable input reaches the pattern and (b) the pattern has nested quantifiers or ambiguous alternation.
+* **NO "Weak Cryptography" Blanket Claims:** MD5 is fine for file-dedupe checksums. Flag only in authentication, integrity, password, or signature contexts.
+* **NO Dependabot Replay:** If the user has not requested a dependency audit, do not produce one. Those findings belong in a separate tool.
+* **NO "Hardcoded Secret" on Placeholders:** `"YOUR_API_KEY_HERE"` or `.env.example` fixtures are not leaked secrets. Confirm entropy and surrounding context.
+
</file context>
This PR introduces two new skills to the collection:
🎨 elite-frontend-design-2026
A complete rework and modernization of the taste skill, rebuilt for April 2026 platform capabilities. Key highlights:
🐛 bugbuster
A brand-new skill focused on forensic bug detection across codebases. Key highlights:
Summary by Sourcery
Add two new specialized skills for frontend design and forensic bug detection to the skills collection.
New Features:
Documentation:
Summary by cubic
Add two new skills to raise output quality:
elite-frontend-design-2026for modern, multi-stack UI work andbugbusterfor forensic, high-signal bug reviews. They codify 2026 platform rules, strict checklists, and clear severity/confidence labeling.elite-frontend-design-2026tailwindcssv4).bugbusterWritten for commit 14a4a48. Summary will update on new commits.
Summary by CodeRabbit
Release Notes