원클릭으로 Manus에서 모든 스킬 실행

nextjs-safe-parallel-work

스타4

포크1

업데이트2026년 5월 20일 07:41

Safe concurrent editing patterns when multiple terminals, agents, or humans are working on the same Next.js codebase. Covers route-group isolation, branch awareness, and conflict avoidance.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Yasuui

Yasuui/hermes-community-skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Next.js Safe Parallel Work

When multiple terminals or agents are editing the same Next.js repo simultaneously:

Core Rules

Always run git status and git branch --show-current first to understand the active branch.
Identify route groups ((marketing), (dashboard), (admin)) and treat them as ownership boundaries.
Never modify files under a route group that another terminal has claimed (user will explicitly state this).
Prefer changes to lib/, types/, supabase/migrations/, and shared API routes that are not marketing-specific.

Pitfalls to Avoid

Touching (marketing)/** when user says another terminal is upgrading the marketing page.
Creating broad refactors that cross route groups.
Committing marketing-related untracked files when the other session is still iterating.

Recommended Workflow

Ask user which route groups or directories are off-limits.
Work only in safe directories (lib/, supabase/migrations/, core API logic, types/).
Use granular commits (one logical change per commit).
Document the safe scope in the commit message.

Session Pattern: Production Hardening While Marketing Upgrade in Progress

When user says "another terminal is upgrading the marketing page":

Explicitly avoid app/(marketing)/**
Focus on: supabase/migrations/, lib/qr/, lib/auth/, app/(dashboard)/**, app/api/** (non-marketing), types/
Example commits from session: migration 004, QR_SECRET hardening, OTP login page update
Always confirm current branch and untracked files before editing

This skill was created after explicit user instruction to avoid marketing page conflicts during parallel work.

이 저장소의 다른 Skills

같은 저장소

browse-sh

Yasuui/hermes-community-skills

Use the browse.sh open-source skill catalog (171+ skills) to interact with websites via their documented APIs or browser automation. Provides precise, token-efficient workflows for weather, flights, jobs, shopping, research, GitHub, and more. Requires `browse` CLI (npm) and Browserbase API key for browser-requiring skills.

2026-05-204

community-skills-marketplace

Yasuui/hermes-community-skills

Design, curate, secure, and ship a Hermes community skills marketplace with a polished skills.sh-style UX.

2026-05-204

daily-debrief-alpha

Yasuui/hermes-community-skills

Morning briefing pattern combining session rehash, tech news, and Polymarket alpha scanning

2026-05-204

daily-note-generator

Yasuui/hermes-community-skills

Generates daily notes for wiki-llm with summary, tasks, focus, token usage, and model tracking

2026-05-204

evolve-bug-fix-may18

Yasuui/hermes-community-skills

Root cause analysis and fix for KeyError on strategy_name during trade logging

2026-05-204

hermes-admin-inspection

Yasuui/hermes-community-skills

Inspect, verify, and troubleshoot Hermes Agent installation state — profiles, memory files, database integrity, configuration, and session logs.

2026-05-204

name	nextjs-safe-parallel-work
description	Safe concurrent editing patterns when multiple terminals, agents, or humans are working on the same Next.js codebase. Covers route-group isolation, branch awareness, and conflict avoidance.
version	1.0.0
category	software-development
license	MIT
tags	["nextjs","concurrency","workflow"]
tested	schema-only
tested_note	Workflow patterns validated at documentation level.

Next.js Safe Parallel Work

When multiple terminals or agents are editing the same Next.js repo simultaneously:

Core Rules

Always run git status and git branch --show-current first to understand the active branch.
Identify route groups ((marketing), (dashboard), (admin)) and treat them as ownership boundaries.
Never modify files under a route group that another terminal has claimed (user will explicitly state this).
Prefer changes to lib/, types/, supabase/migrations/, and shared API routes that are not marketing-specific.

Pitfalls to Avoid

Touching (marketing)/** when user says another terminal is upgrading the marketing page.
Creating broad refactors that cross route groups.
Committing marketing-related untracked files when the other session is still iterating.

Recommended Workflow

Ask user which route groups or directories are off-limits.
Work only in safe directories (lib/, supabase/migrations/, core API logic, types/).
Use granular commits (one logical change per commit).
Document the safe scope in the commit message.

Session Pattern: Production Hardening While Marketing Upgrade in Progress

When user says "another terminal is upgrading the marketing page":

Explicitly avoid app/(marketing)/**
Focus on: supabase/migrations/, lib/qr/, lib/auth/, app/(dashboard)/**, app/api/** (non-marketing), types/
Example commits from session: migration 004, QR_SECRET hardening, OTP login page update
Always confirm current branch and untracked files before editing

This skill was created after explicit user instruction to avoid marketing page conflicts during parallel work.