Skip to main content
在 Manus 中运行任何 Skill
一键导入
petreleon
GitHub 创作者资料

petreleon

按仓库查看 2 个 GitHub 仓库中的 9 个已收集 skills。

已收集 skills
9
仓库
2
更新
2026-06-08
仓库浏览

仓库与代表性 skills

automatic-tester
软件质量保证分析师与测试员

Automated frontend, backend, and runtime test creation/execution for RustLearn or similar Rust/Next.js apps: Rust contract tests, API helper tests, route guard tests, Playwright/e2e checks, Docker Compose and Kubernetes smoke/log verification. Use when asked to add, run, debug, or harden repeatable tests.

2026-06-08
backend-dev
软件开发工程师

Implement RustLearn backend/API work in Rust Actix Web with Diesel/PostgreSQL, repository/service layers, permission-scoped authorization, migrations, workers, wallets, reports, and frontend contract endpoints. Use when Codex is asked to add, fix, or refactor backend contracts, handlers, services, repositories, migrations, or Rust tests.

2026-06-08
frontend-dev
网页开发工程师

Implement product-grade frontend work for RustLearn or similar Next.js/React apps: app shell, auth/session UI, learner/teacher/organization/admin routes, permission-aware components, forms, data helpers, responsive layout, and UX refactors. Use when Codex is asked to build, refactor, or fix frontend code rather than only plan or test it.

2026-06-08
manual-tester
软件质量保证分析师与测试员

Manual rendered frontend QA for RustLearn or similar web apps through Browser/Playwright: inspect desktop/mobile UI, exercise user flows, verify copy/states/permissions, capture screenshots, and report findings. Use when asked to manually test, QA, inspect, reproduce, or validate frontend user flows.

2026-06-08
product-manager
项目管理专家

Frontend product management for RustLearn or similar product work: sequence milestones, update TODO roadmap, define dependencies, cut scope, identify risks, and turn goals into implementation plans. Use when asked to plan, prioritize, break down, roadmap, or coordinate frontend development.

2026-06-08
product-owner
项目管理专家

Frontend product ownership for RustLearn or similar product work: define persona value, user stories, acceptance criteria, scope boundaries, and done/not-done decisions. Use when asked to decide what a frontend feature must do for users, write acceptance criteria, or judge whether a flow is acceptable.

2026-06-08
已展示 2 / 2 个仓库
已展示全部仓库