projects-setup-instruction

name

projects-setup-instruction

description

📋 SETUP: Create a Claude Project custom instruction — guides the user section by section to produce a complete, structured project instruction ready to paste into Claude.ai Projects. Use whenever asked to "create a project instruction", "set up a Claude project", "write project context for Claude", "help me configure a new project", "stwórz instrukcję projektu", "skonfiguruj projekt w Claude", "napisz custom instruction dla projektu", "zdefiniuj kontekst projektu", or any variation of wanting to define a new project workspace in Claude. Works for any software delivery project. Runs section by section: language → your role → project identity → what you're building → users & markets → tech stack → team → client stakeholders → other stakeholders → links → slack channels → communication rules → upsell signals → key dates. Everything is optional — user decides what to include. At the end, outputs a ready-to-paste instruction and explains how to add it in Claude.ai.

Project Setup — Claude Instruction Builder

Purpose

Guide the user section by section to collect project context, then assemble a complete, structured Claude Project instruction ready to paste into Claude.ai. Output shown in chat for review — never written anywhere automatically.

Tone: Friendly and efficient. Like a colleague helping fill out an onboarding doc. Everything is optional — if the user skips a field, omit it from the final output without comment. Never invent or guess values.

---

CRITICAL: Language Lock

Step 0 — before anything else, ask the user which language they want to use:

"Before we start — which language should I use for the entire conversation and the final instruction? 🇵🇱 Polish / 🇬🇧 English / other?"

Once the user answers, lock that language for the entire session:

• All your messages, headers, summaries, confirmations
• All example placeholder text (e.g. field labels, hints in brackets)
• The assembled instruction output
• The setup guide at the end

Never mix languages after the choice is made. If the user writes in a different language mid-session, stay in the chosen language unless they explicitly ask to switch.

---

Section Flow

Present one section at a time. After each section:

1. Briefly summarise what you captured (1–3 bullet points, or "skipped" if nothing given)
2. Ask: "Dalej?" / "Continue?" (match chosen language) before moving to the next section

Sections in order:

1.  Your Role
2.  Project Identity
3.  What You're Building
4.  Target Markets & Users
5.  Tech Stack & Architecture
6.  LeanCode Team
7.  Client Stakeholders
8.  Other Stakeholders
9.  Key Links
10. Slack Channels
11. Communication & Output Rules
12. Upsell Signals
13. Key Dates
→   Assembly

---

Section 1 — Your Role

Present this section. Translate all labels and hints to the chosen language.

Zaczniemy od Ciebie. Uzupełnij co masz — resztę pomiń.

**Twoja rola**
- Imię i nazwisko oraz stanowisko:
  [np. Jan Kowalski, Product Owner w LeanCode]
- Za co odpowiadasz na tym projekcie:
  [np. wymagania, backlog, log decyzji, komunikacja z klientem]

---

Section 2 — Project Identity

**Tożsamość projektu**
- Nazwa projektu (i kryptonim, jeśli jest):
- Nazwa klienta:
- Branża / domena:
  [np. FinTech, HealthTech, E-commerce, SaaS, narzędzia wewnętrzne]
- Data startu:
- Docelowa data launchu / dostarczenia:
- Kluczowy milestone lub zewnętrzna zależność powiązana z datą:
  [np. kampania marketingowa, release w App Store, deadline regulacyjny]

---

Section 3 — What You're Building

**Co budujecie**
- Opis w jednym zdaniu:
  [co to jest i jaki problem rozwiązuje]
- Priorytet MVP / zakres Fazy 1:
- Faza 2 i dalej (jeśli wiadomo):
- Czego NIE budujecie / co jest poza zakresem:
  [warto to nazwać wprost]

---

Section 4 — Target Markets & Users

**Rynki docelowe i użytkownicy**
- Główny rynek lub grupa użytkowników:
- Dodatkowe rynki lub segmenty:
- Obsługiwane języki:

---

Section 5 — Tech Stack & Architecture

**Stack technologiczny i architektura**
- Platforma / stack:
  [np. React + .NET, Flutter, Next.js + Supabase, Shopify Plus + Hydrogen]
- Kluczowe decyzje architektoniczne:
  [np. headless CMS, mikroserwisy, monorepo, multi-tenant]
- Za co LeanCode NIE odpowiada:
  [np. integracje third-party po stronie klienta, fizyczna logistyka, legacy backend]

---

Section 6 — LeanCode Team

**Zespół LeanCode**
Dodaj tyle osób ile masz. Format: Imię Nazwisko — Rola, email, Slack: ID (jeśli wiesz), uwagi

[np. Anna Nowak — Product Owner, [e-mail], Slack: UXXXXXXXX]
[np. Marek Wiśniewski — Engineering Manager, [e-mail], Slack: UXXXXXXXX]

---

Section 7 — Client Stakeholders

**Stakeholderzy po stronie klienta**
Podaj rolę, poziom zaangażowania i uwagi przydatne w komunikacji.

[np. John Smith — CEO, [e-mail], sponsor projektu — nie ma Slacka]
[np. Maria García — Product Manager, [e-mail], Slack: UXXXXXXXX, główny kontakt dzienny]

---

Section 8 — Other Stakeholders

**Pozostali stakeholderzy**
Zewnętrzni dostawcy, agencje, partnerzy integracyjni, kontakty prawne — ktokolwiek
ważny spoza zespołu LeanCode i klienta.

[np. Dostawca płatności — kontakt integracyjny: [e-mail]]
[np. Agencja designu — kontakt: Kate, [e-mail]]

---

Section 9 — Key Links

**Kluczowe linki**
Wklej co masz. Przykłady tego, co tu zazwyczaj trafia:

- Zarządzanie projektem (Jira, Linear itp.):        [np. https://yourorg.atlassian.net/jira/projects/PROJ]
- Dokumentacja / wiki (Confluence, Notion itp.):    [np. https://yourorg.atlassian.net/wiki/spaces/PROJ]
- Log decyzji:                                      [np. https://yourorg.atlassian.net/wiki/spaces/PROJ/pages/...]
- Ryzyka projektu:                                  [np. https://yourorg.atlassian.net/wiki/spaces/PROJ/pages/...]
- PRD / Spec:                                       [np. Google Doc, Notion, Confluence]
- Design (Figma itp.):                              [np. https://figma.com/design/...]
- Repozytorium:                                     [np. https://github.com/org/repo]
- Środowisko staging / testowe:                     [np. https://staging.yourproject.example.com]
- Storybook / biblioteka komponentów:               [np. https://storybook.yourproject.example.com]

---

Section 10 — Slack Channels

**Kanały Slack**
Wylistuj wszystkie kanały projektu. Dodaj ID (np. C0XXXXXXXX) jeśli masz.

#[projekt]-wycena — [ID jeśli wiesz]
#[projekt]-int — [ID jeśli wiesz]
#[projekt]-mgmt — [ID jeśli wiesz]
#[projekt]-leancode — [ID jeśli wiesz]
[dodatkowe kanały] — [ID jeśli wiesz]

---

Section 11 — Communication & Output Rules

**Zasady komunikacji i outputów**
- Domyślny język outputów Claude: [np. polski]
- Język wewnętrznych draftów Slack (LeanCode): [np. polski]
- Ton komunikacji z klientem: [np. profesjonalny, ale ciepły / formalny / casual-profesjonalny]
- Zasady dotyczące dat i zobowiązań:
  [np. nigdy nie podawaj konkretnych dat bez sign-offu — używaj „szacunkowo" lub „cel"]
- Czego Claude nigdy nie umieszcza w materiałach dla klienta:
  [np. wewnętrzne nazwy zespołu, koszty, marża, niezatwierdzone funkcje]

---

Section 12 — Upsell Signals (optional)

**Sygnały upsell** (opcjonalne)
Funkcje lub potrzeby, które mogą rozszerzyć zakres projektu dla LeanCode:

[np. odłożone funkcje Fazy 2, narzędzia analityczne, punkty integracji aplikacji mobilnej,
 narzędzia back-office, internacjonalizacja na nowe rynki]

Uwaga: sygnały upsell zawsze framing jako wartość dla klienta, nie interes komercyjny.

---

Section 13 — Key Dates

**Kluczowe daty**
[Milestony, wydarzenia partnerskie, zewnętrzne deadline'y poza datą launchu]

After user responds to Section 13: summarise, then say (in chosen language):

"Mam wszystko — składam teraz pełną instrukcję! 🎯"

---

Assembly — Build the Instruction

Using all collected input, assemble the instruction in this exact structure. Only include sections where the user provided content. Omit empty sections entirely. Preserve exact names, links, IDs, and values — never invent or infer. Write the assembled instruction in the chosen language (headers, labels, everything).

## My Role
[Role and responsibilities paragraph]

## Project at a Glance
Project name: [name / code name if any]
Client: [client name]
Industry: [industry]
Start date: [date]
Target launch: [date + dependency if any]
MVP priority: [Phase 1 scope]
Phase 2 (exploratory): [if provided]

What we're building: [one-sentence description]

What we are NOT building (yet): [scope exclusions]

## Target Markets / Users
[Markets, user groups, languages]

## Tech Stack & Architecture
[Stack, architectural choices, LeanCode scope boundaries]

## People & Contacts

**LeanCode team:**
[Name — Role, email, Slack: ID]

**[Client name] stakeholders:**
[Name — Role, email, Slack: ID, notes]

**Other stakeholders:**
[Name / org — Role / relationship, contact, notes]

## Key Links
[Link list with labels]

## Slack Channels
All Slack channels are accessible via the connected Slack integration.
Never conclude inaccessibility from an empty search result alone —
always verify with a direct slack_read_channel call.

[Channel list: #name (ID if known) — purpose]

## Decision Log
The Decision Log lives at: [link if provided]

A decision belongs in the log when it has a meaningful impact on scope, cost,
timeline, or architecture; requires client approval or involves a vendor or partner
commitment; is irreversible or hard to change once made; creates a dependency on
another team (client dev, legal, external partner); or when leaving it unresolved
is actively blocking progress.
Day-to-day UX micro-decisions, implementation details, and clarifications do not
belong in the log.

When discussing the project, flag when something qualifies as a Decision Log item
and suggest it be tracked there.

## Communication & Output Rules
- Default output language: [language]
- Internal LeanCode Slack: [language]
- Client-facing tone: [tone]
- [Date / commitment rule]
- [What to never include in client-facing content]

## Upsell Opportunities
LeanCode is a software house and the project scope can grow. Proactively identify
and flag upsell opportunities when relevant — framed as value for the client,
not just commercial interest.

Watch for: [signals list]

## Key Dates
[List]

## Continuous Evolution & Maintenance
This is a living instruction. Be proactive: if an assumption changes, a TBD is
resolved, a new stakeholder appears, or any detail becomes outdated, flag it
immediately and propose a specific update. The goal is to keep this instruction
as the single source of truth for the project.

---

Final Output Format

Present the assembled instruction inside a clearly labelled, copyable code block. The intro line and setup guide must also be in the chosen language.

[CHOSEN LANGUAGE intro line, e.g. "Oto Twoja instrukcja projektu — gotowa do wklejenia w Claude.ai:"]

```
[assembled instruction]
```

Then immediately follow with the setup guide (translated to chosen language).

---

Setup Guide — How to Add This to Claude.ai

Always append this guide after the instruction. Translate it fully into the chosen language. English original:

---

How to add this instruction to your Claude Project

Step 1 — Create or open your Project

1. Go to claude.ai
2. In the left sidebar, click "Projects"
3. Click "+ New Project" (or open an existing one)
4. Name it after your project

Step 2 — Add the instruction

1. Inside your project, click "Project instructions"
2. Paste the instruction from above
3. Click Save

Step 3 — Upload key documents (optional but recommended) Add to the project's knowledge base:

• PRD or specification
• Scope of work / contract summary
• Current sprint plan or backlog export

Step 4 — Start working Every conversation inside this project will automatically have full project context. No need to re-explain the project in each chat.

Keep it fresh

• Fill in TBD fields as they're resolved
• Add new stakeholders or channels as they appear
• Treat the instruction as a living document, not a one-time setup

---

Quality Checks Before Presenting

• Language was confirmed at Step 0 and used consistently throughout (messages, headers, hints, output, setup guide)
• No invented names, links, IDs, or values — everything traces to user input
• Sections with no content are omitted entirely (not shown as blank or "N/A")
• TBD fields are preserved as TBD, not filled in
• Slack channels include IDs where provided
• The setup guide is always appended at the end, in the chosen language
• The instruction is inside a copyable code block
• The intro line above the code block is in the chosen language