lennney
- 118 skills
- 0 followers
- 1 repo stars
- last month last updated
- ▌ Gate Testcov · lennney测试覆盖 / Test coverage. Adds tests for core functionality. Use when the user wants to add test coverage to their project.
- ▌ E2e Playwright · lennneyEnd-to-end testing with Playwright in Next.js applications — user flow coverage, component testing, and CI integration. Use when writing E2E tests, debugging flaky tests, or setting up test infrastructure.
- ▌ Error Handling · lennneyFrontend error handling patterns for Next.js — error boundaries, API error display, form validation errors, and global error recovery strategies. Use when implementing error states, debugging error UI, or designing error recovery flows.
- ▌ Gate Frontend · lennney前端开发 / Frontend development. Builds pages and components from project scaffold. Use when the project is initialized and the user wants to build the UI.
- ▌ Gate Optimize · lennney网站优化 / Site optimization. Routes users to perf, a11y, or animation optimization. Use when the site is live and the user wants to improve it.
- ▌ Product Analysis · lennneyMulti-path parallel product analysis with cross-model test-time compute scaling. Spawns parallel agents (Claude Code agent teams + Codex CLI) to explore product from multiple perspectives, then synthesizes findings into actionable optimization plans. Can invoke competitors-analysis for competitive benchmarking. Use when "product audit", "self-review", "发布前审查", "产品分析", "analyze our product", "UX audit", or "信息架构审计".
- ▌ Code Review Skill · lennney bundleComprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, PHP, Python, Django, Go, C#/.NET, Kotlin, Swift, NestJS, C/C++, and more. Helps catch bugs, improve code quality, and give constructive feedback. Use when reviewing pull requests, conducting PR reviews, code review, reviewing code changes, establishing review standards, mentoring developers, architecture reviews, security audits, checking code quality, finding bugs, giving feedback on code.
- ▌ Prd Development · lennney bundleBuild a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
- ▌
- ▌
- ▌ Frontend Designer · lennneyBuild accessible, responsive, and performant frontend components with design system best practices, modern CSS, and framework-agnostic patterns.
- ▌ Component Design · lennneyDesign React/Next.js component APIs with clear Server/Client boundaries, composable patterns, and proper seam placement. Use when designing new components, refactoring existing ones, or deciding between Server/Client Component boundaries.
- ▌
- ▌ Salgadoia Web Design Engineer Pro · lennneyProfesional web & landing page builder with Next.js 16, React 19, Tailwind CSS v4, shadcn/ui, and Framer Motion. 用 Next.js 16 + React 19 + Tailwind CSS v4 + shadcn/ui 构建专业落地页。8 种视觉方向、10 套色板、10 组字体搭配。 用户说"帮我建个落地页"、"做一个官网"、"设计一个 landing page"时加载。
- ▌ Diagnosing Bugs · lennneyDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
- ▌ Acceptance Criteria · lennney bundleWrite testable acceptance criteria and acceptance tests for requirements using Given/When/Then, checklist, and rule-based formats. Use when defining the conditions that prove a requirement is correctly implemented.
- ▌ Styleseed Design Review · lennneyReviews UI/frontend code and tells you exactly why it "looks AI-generated" — then how to fix it. Use it when a React/Tailwind/HTML interface looks off, generic, or unfinished, when you want a design score before shipping, or when asked to make UI look more professional, polished, or "designed, not generated." Self-contained; based on the open-source StyleSeed design engine.
- ▌ Stss · lennney bundleReduce defensive disclaimers, stacked hedging, and self-protective narration in proposals and decision-facing writing. Use when the user asks to rewrite or audit a proposal, plan, research contribution, executive summary, or similar text for directness. Do not use for ordinary code work or unrelated prose.