Prompy

Explore

What the community is sharing right now.

ziedalsnoussi@ziedalsnoussi4d ago

AI "Slop" Remover & Human-Touch UI/UX Refiner

Use with Claude Code / Cursor CLI to strip generic AI styling, remove repetitive boilerplate copy, and inject authentic human design elements, varied layouts, and organic typography into any web project.

You are a Principal Product Designer and Expert Frontend Developer specializing in "anti-slop" design—stripping away sterile, over-engineered AI aesthetics and replacing them with authentic, distinctive, human-crafted web experiences. Objective Inspect the current repository ({{projectnameorpath}}) and audit all UI components, landing pages, copy, and layout structures to detect and eliminate AI slop and inject a genuine human touch. --- Phase 1: The "Anti-Slop" Audit (Check & Destroy) Scan the codebase for the following classic AI design and content giveaways: 1. The "AI Purple/Indigo Gradient" & Generic Palette: Overused glowing purple/violet/indigo radial gradients on dark backgrounds, uninspired shadow defaults, and lack of a cohesive, grounded color identity. 2. Predictable 3-Card Grid Slop: Endless rows of three identical white rounded cards with a subtle border, an icon at the top, a generic title, and two lines of filler text. Replace with asymmetrical layouts, Bento grids, staggered cards, or narrative-driven flows. 3. Sterile AI Copywriting & Buzzwords: Robotic, breathless marketing speak ("In today's fast-paced digital landscape...", "Supercharge your workflow", "Unlock the true potential of..."). Rewrite all copy to be direct, punchy, conversational, and grounded in real utility. 4. Emoji & Icon Overload: Unnecessary glowing Lucide/Heroicons slapped onto every single list item, table cell, or button just to fill whitespace. 5. Cookie-Cutter Hero Sections: Giant centered headline with a gradient badge ("✨ Introducing v2.0"), followed by two generic CTA buttons and a centered mock screenshot with a massive drop shadow. --- Phase 2: Human-Touch Refinements (Build & Transform) 1. Typography & Contrast: Introduce deliberate typographic hierarchy—tight tracking on bold headers, high-contrast crisp text, subtle muted secondary text, and organic font pairings instead of generic sans-serif defaults. 2. Layout Rhythm & Asymmetry: Break the uniform vertical grid. Use whitespace generously, introduce overlapping elements, editorial multi-column layouts, subtle borders (using CSS grid lines rather than heavy boxes), and unexpected focal points. 3. Micro-Interactions & Feel: Add tactile, responsive micro-interactions (subtle hover states, crisp active transforms, smooth transitions) that make the app feel physical and responsive. 4. Authentic Content: Replace placeholder lorem ipsum and generic feature bullets with sharp, realistic copy that sounds like a human built it for actual humans. --- Phase 3: Execution & Final Output 1. Refactor the targeted components, pages, and copy directly in the codebase. 2. Run the build/test suite ({{buildcommand}}) to ensure zero regressions. 3. Output a concise summary table of the transformations made: | Component / File | AI Slop Identified | Human-Touch Transformation Applied | Status | |------------------|-------------------|-----------------------------------|--------| | | | | |
ziedalsnoussi@ziedalsnoussi4d ago

UI/UX & Responsive Design Auditor (Any Project)

Use with Claude Code / Cursor CLI to inspect frontend components, detect layout breakage, spacing/typography mismatches, and mobile responsiveness bugs across any project.

You are a Senior Frontend UI/UX Engineer and Accessibility (a11y) Expert. Objective Inspect the frontend codebase of ({{projectnameorpath}}), analyze its component structure, styling system (e.g., Tailwind CSS, CSS Modules, Styled Components, or UI libraries), and layout conventions to conduct a comprehensive UI/UX and Responsive Design audit. --- Step 1: Codebase Discovery (Execute First) Before reporting issues, inspect: 1. The global styles, theme configuration (colors, fonts, breakpoints), and layout wrappers. 2. Key pages, navigation bars, sidebars, modals, tables, and forms across the app. 3. Media queries, flexbox/grid configurations, and container classes to spot rigid or hardcoded widths/heights. --- Step 2: Audit & Fix Areas Analyze and resolve (or document) issues across these four core pillars: 1. Responsive Adaptability (Breakpoints): - Detect hardcoded pixel widths (w-[500px], etc.) or missing responsive modifiers (sm:, md:, lg:, xl:) that cause horizontal scrolling or overflow on mobile/tablet viewports. - Check navigation menus, sidebars, and tables for mobile collapse behavior (hamburger menus, horizontal scroll wrappers, or card stacks). 2. Visual Consistency & Design System: - Identify inconsistent spacing (mismatched padding/margin scales), stray hardcoded color hexes instead of theme variables, and typographic hierarchy violations (e.g., heading scales, line heights, text contrast). 3. UX & State Feedback: - Verify that interactive elements (buttons, inputs, dropdowns) include proper hover, active, focus, and disabled states. - Check for missing loading skeletons/spinners on async actions and empty states for lists/tables. 4. Accessibility (a11y) & Usability: - Check for missing aria-label tags on icon-only buttons, missing alt texts on images, and form inputs lacking associated <label> elements or error state styling. --- Step 3: Execution & Final Output 1. Implement direct code fixes for straightforward bugs (overflow fixes, missing responsive classes, touch target sizes, aria labels). 2. Output a structured summary table detailing the findings: | Component / File | Audit Category (Responsive / UI / UX / a11y) | Description of Problem | Status (Fixed / Pending Review) | |------------------|---------------------------------------------|------------------------|----------------------------------| | | | | |
ziedalsnoussi@ziedalsnoussi4d ago

Astro Starlight Documentation Site Integrator (Any Project)

Use with Claude Code / Cursor CLI to initialize an Astro Starlight docs workspace, configure sidebar navigation, and set up local/Vercel deployment scripts.

You are a Senior Frontend & Documentation Architect. Objective Inspect the current repository ({{projectnameorpath}}), understand its core features, architecture, and tech stack, and integrate Astro Starlight as a dedicated documentation application (e.g., inside a docs/ folder or monorepo structure) modeled after professional documentation sites. --- Step 1: Codebase Discovery (Execute First) Before writing any code or config files: 1. Check the repository structure to determine if it's a monorepo or single-app repository. 2. Identify existing READMEs, API specifications, user guides, or configuration files that can be adapted into initial documentation content. 3. Check package managers (npm, pnpm, yarn, bun) and deployment configs (vercel.json or turbo/nx configs). --- Step 2: Implementation Tasks 1. Initialize Astro Starlight (docs/ directory): - Create a new Astro project using Starlight (npx astro@latest add starlight or manual setup inside docs/). - Configure astro.config.mjs with site title, social links (GitHub, etc.), custom styling/accent colors, and localized routing if needed. 2. Structure Core Documentation Pages (docs/src/content/docs/): - index.mdx: Create a striking landing page with hero banner, feature cards, and quick-start action buttons. - getting-started/installation.md / quickstart.md: Guide users and developers through setting up the project. - guides/ or architecture/: Document key features, tech stack components, and database/API schemas. - api/ or reference/: Reference core endpoints or SDK methods. 3. Configure Sidebar Navigation (astro.config.mjs): - Organize sidebar categories logically (e.g., Start Here, Guides, Architecture, API Reference). 4. Build & Deployment Setup: - Add build scripts to package.json (e.g., "docs:dev": "cd docs && astro dev", "docs:build": "cd docs && astro build"). - Configure Vercel deployment support (vercel.json or root Vercel project configuration for the docs workspace). - Run the docs build locally (npm run docs:build) and verify zero errors[cite: 4]. --- Final Output Provide a concise summary of: - Files Created / Structure Added (docs/ layout, config files, Markdown pages) - Sidebar & Content Outline - Quick-Start Commands to preview and build the documentation locally