Permits — 1 of 20 skills in the Architect & BTP pack
In a chat, Word or Excel files aren't always generated: you get the document as structured text instead.
Permis-Construire
The support documents to put together a building-permit application.
Free, no account, no email — the command is all you need.
Already have it?
Nothing to install if it's already active
If this skill is already added in your Claude, there's no need to install it again. Just ask for what you want to do.
Not sure? Ask Claude: "which skills do you have available?"
“Use the building-permit skill to prepare the required-pieces checklist and descriptive notice for this project: …”
1 · The simplest way
Copy and paste into any AI chat
This button copies the whole skill. Paste it into Claude, ChatGPT, or Gemini, then describe what you need. No installation required.
In a chat, Word or Excel files can't always be generated: you'll receive the document as structured text instead, and Claude will flag it.
2 · Command line
/permis-construire installs in 3 steps
For Claude Code. The skill installs on your computer and stays available across all your projects.
Prerequisites: Claude Code + Node.js
The skill runs inside Claude Code, Anthropic's AI assistant installed on your computer. Node.js is the engine that runs the install command. Both are free.
Open PowerShell
Click Start, type "PowerShell", then press Enter.
Paste the command
Right-click inside the PowerShell window (or press Ctrl + V) to paste the command below, then press Enter. Wait a few seconds.
npx educasium --skill permis-construire --globalWhat you should see:
npx educasium --skill permis-construire --global
Fetching https://raw.githubusercontent.com/Chappygo-OS/claude-meta-skills/main/dist/permis-construire.zip
…
Installed "permis-construire". Restart Claude Code to pick it up.
Restart Claude Code
In Claude Code, type /restart (or quit and relaunch Claude Code). The skill now appears in the command list.
Don't use a terminal?
Using Claude.ai in your browser?
The assisted install works through a .zip file imported into Claude.ai. It takes longer and asks for your email.
What the skill does
View the source codeIn detail.
Describe the project (protected zone or not). Claude generates the required-pieces checklist (.xlsx) and the PCMI4 descriptive notice (.docx), plus the deposit summary. Doesn't fill the CERFA form or produce plans.
When to use it
You're putting together a building-permit application and need the checklist and notice.
Example usage
/permis-construire PC for a single-family home in Brest, do the checklist and notice...In depth
How this skill really works
Permis-Construire produces the support documents for a French Permis de Construire (PC) or PCMI application — a personalized checklist of required pieces (.xlsx), the PCMI4 descriptive notice (.docx), and the deposit summary/bordereau (.docx). It doesn't fill the CERFA forms themselves (13406*13 for a single-family-home PCMI, 13409*13 for any other PC) and doesn't produce plans, photos, or technical studies: it's the textual and administrative backbone of the file, not the complete application.
The Code de l'urbanisme strictly governs this content (articles R421-1 and following for scope, R431-1 and following for the file's content) and requires an architect above 150 m² of floor area for individuals (art. R431-2). The instruction period is 2 months for a PCMI and 3 months for a PC, extended by a month if the project sits in an ABF, ERP, or IGH zone — a status the skill always asks about first, since it changes both the checklist and the timeline announced to the client.
It's built for the architect assembling a PC/PCMI file who wants to produce the checklist and notice without rebuilding their structure on every project, while explicitly flagging what it doesn't produce (CERFA, plans, studies) rather than implying the file is complete.
When to use it
- At the start of a PC or PCMI file, to produce the pieces checklist and the descriptive notice.
- When the project's ABF status (notable heritage site, historic-monument surroundings, listed/registered site) needs establishing before knowing which pieces to request.
- When the PCMI4 notice needs to cover the 6 sections the reviewer expects (land, project, insertion, materials/colors, surroundings, PLU compliance).
- When a formal deposit summary is needed for filing at the town hall, with the right number of copies.
- When conditional pieces need identifying based on the situation (RE2020, soil study, ERP, ICPE).
- When a demolition needs folding into the same file ahead of rebuilding, rather than being filed separately.
When not to use it
- Does not determine on its own whether the project needs a PC/PCMI or only a lighter déclaration préalable — that classification depends on surface and zoning thresholds the skill doesn't automatically check; when in doubt about lighter works, refer to /declaration-prealable instead.
- Does not replace the town hall's review of the file, nor an opinion from the Architecte des Bâtiments de France in a protected zone — it prepares supporting pieces; the decision stays with the administration.
- Does not fill CERFA forms 13406*13 or 13409*13 themselves.
- Does not produce the plans, photos, or technical studies the file requires (RE2020, soil study) — only their absence is flagged in the final report.
The method
The checklist / notice / deposit-summary triptych
references/structure-pc.md documents 3 complementary deliverables, all gated by the same ABF status collected upfront: the required-pieces table (PCMI1-8, plus conditional and ABF-specific pieces), the 6-section structure of the PCMI4 notice, and the deposit-summary format.
- Mandatory pieces (PCMI1-8)
- Eight numbered pieces: site plan, layout plan, cross-section, descriptive notice, elevations and roof plan, insertion graphic, and two photos (near and distant surroundings).
- Conditional pieces
- RE2020 certificate for new construction >50 m², a soil study in clay shrink-swell risk zones, an interior plan and accessibility certificate for an ERP, an impact study for an ICPE, an ABF notice in a protected zone.
- PCMI4 notice (6 sections)
- Land, project, environmental insertion, materials and colors, surroundings treatment, regulatory compliance — in that order, so the reviewer can understand the project without seeing the plans.
- Deposit summary
- Numbered table of pieces with the expected number of copies (4 for PCMI, 5 for PC, plus extra copies if ABF applies) and an administrative header (project, address, applicant, architect, filing date, town hall).
Steps
Identify the file type and ABF status
Determine PCMI (CERFA 13406*13, single-family home) or PC (CERFA 13409*13, other), and always ask about ABF status if not stated — it changes both the checklist and the instruction period.
Collect the information
Common project information (nature, address, cadastral references, surfaces, height, use), regulatory information (PLU zone, coverage-ratio/height/setback rules, risk zone), and applicant information (name, capacity, architect if applicable).
Build the requested documents
Read references/structure-pc.md for the full required-pieces table (standard, conditional, ABF), the 6-section PCMI4 notice structure, and the deposit-summary format.
Generate the files
Checklist in .xlsx, notice and deposit summary in .docx. Name them Checklist-PC-[ProjectName].xlsx, Notice-PCMI4-[ProjectName].docx, Bordereau-depot-PC-[ProjectName].docx.
Report
List which documents were generated, flag any missing piece the checklist surfaced (plans, photos, technical studies this skill doesn't produce), and remind the user these are support documents, not the CERFA form itself.
Rules
- Always ask about ABF status if not stated — it changes the checklist and adds a month to the instruction period.
- Distinguish PCMI (CERFA 13406*13, single-family home) from PC (CERFA 13409*13, other) from the first reply.
- Follow the order of the PCMI4 notice's 6 sections: land, project, insertion, materials/colors, surroundings, PLU compliance.
- Name files following Checklist-PC-[ProjectName].xlsx, Notice-PCMI4-[ProjectName].docx, Bordereau-depot-PC-[ProjectName].docx.
- Never fill CERFA forms 13406*13 or 13409*13 — that's not this skill's role.
- Explicitly flag at the end of generation any piece (plan, photo, study) the file needs that this skill doesn't produce.
Mistakes to avoid
- Treating this skill as sufficient to file a complete application when it produces neither the CERFA nor plans.
- Skipping the ABF status question, which nonetheless changes the checklist and the instruction period.
- Using this skill for a project that actually only needs a déclaration préalable — a mix-up with /declaration-prealable.
- Skipping a section of the PCMI4 notice instead of filling it with an explicit placeholder when information is missing.
- Improvising the number of copies expected at the town hall instead of following the documented rule (4 for PCMI, 5 for PC).
What this skill doesn't do
- Does not fill CERFA forms 13406*13 or 13409*13.
- Does not produce plans (site, layout, sections, elevations), photos, or technical studies (soil study, RE2020 certificate).
- Does not determine whether the project needs a PC/PCMI rather than a déclaration préalable — that classification remains the architect's judgment, not an automatic check by the skill.
- Does not replace the town hall's review of the file, nor the opinion of the Architecte des Bâtiments de France in a protected zone.
- Does not handle a prior demolition filed as a separate application — see /permis-demolir.
- Does not track the file's progress after filing (requests for additional pieces, follow-ups from the town hall).
Skill contents — 2 fichiers · 8.8 KB(SKILL.md, references/structure-pc.md)
Download for free