Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

frontend-workspace-change

Étoiles0

Forks0

Mis à jour4 avril 2026 à 09:15

Use this skill when changing the Next.js workspace UI, especially resume, JD, tailored resume, or mock interview flows inside the authenticated dashboard.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

zhengwenze

zhengwenze/CareerPilot

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	frontend-workspace-change
description	Use this skill when changing the Next.js workspace UI, especially resume, JD, tailored resume, or mock interview flows inside the authenticated dashboard.

Frontend Workspace Change

Use this skill when a task touches apps/frontend/.

Goals

preserve the single-workspace feel of Career Pilot
keep resume, job description, tailored resume, and mock interview connected
avoid turning workflow screens into isolated marketing-style pages

Read first

AGENTS.md
docs/codex-workspace.md
apps/frontend/AGENTS.md
the relevant route, component, and API module

Working rules

inspect existing route and layout structure before adding components
prefer editing existing dashboard and workflow components over adding parallel abstractions
keep async states explicit: loading, empty, success, failure, retry
if backend contract assumptions change, update the affected API client and UI in the same task
preserve the handoff from tailored resume output into mock interview entry

Validation

Run the narrowest useful check in apps/frontend/:

npm run dev

Plus depuis ce dépôt

même dépôt

dual-repo-publish

zhengwenze/CareerPilot

Use this skill when the user wants one-shot commit-and-push sync for Career Pilot to Gitee master and GitHub main with Conventional Commits.

2026-04-140

git-commit-convention

zhengwenze/CareerPilot

Use this skill when the user wants to write, rewrite, validate, or improve Git commit messages using Conventional Commits. Helps classify changes, split mixed work into logical commits, choose scopes, detect breaking changes, and produce clear commit messages in the format type(scope): description.

2026-04-140

git-pre-commit-check

zhengwenze/CareerPilot

Use this skill to perform pre-commit checks including sensitive data scanning, large file detection, code quality validation, and test reminders before creating Git commits.

2026-04-090

mock-interview-session

zhengwenze/CareerPilot

Use this skill when changing mock interview session creation, question flow, answer submission, follow-up logic, review output, or session lifecycle behavior.

2026-04-050

resume-pipeline

zhengwenze/CareerPilot

Use this skill when working on the master-resume workflow from file upload through Markdown editing, persistence, and downstream structured reuse.

2026-04-050

tailored-resume-contract

zhengwenze/CareerPilot

Use this skill when changing the contract and workflow that connects saved jobs, match data, tailored resume generation, retry state, download, and interview handoff.

2026-04-050

name	frontend-workspace-change
description	Use this skill when changing the Next.js workspace UI, especially resume, JD, tailored resume, or mock interview flows inside the authenticated dashboard.

Frontend Workspace Change

Use this skill when a task touches apps/frontend/.

Goals

preserve the single-workspace feel of Career Pilot
keep resume, job description, tailored resume, and mock interview connected
avoid turning workflow screens into isolated marketing-style pages

Read first

AGENTS.md
docs/codex-workspace.md
apps/frontend/AGENTS.md
the relevant route, component, and API module

Working rules

inspect existing route and layout structure before adding components
prefer editing existing dashboard and workflow components over adding parallel abstractions
keep async states explicit: loading, empty, success, failure, retry
if backend contract assumptions change, update the affected API client and UI in the same task
preserve the handoff from tailored resume output into mock interview entry

Validation

Run the narrowest useful check in apps/frontend/:

npm run dev