symfony-sk:check-config
Verify project configuration before using other skills/agents. Creates .claude/project.json if missing.
What this skill does
# Check Config Skill
## Mission
Verify that the project is properly configured for Symfony StarterKit plugin. This skill is called automatically by agents before they start their work.
---
## Verification Steps
### 1. Check if `.claude/project.json` exists
```bash
# File should exist at project root
.claude/project.json
```
### 2. If missing, gather information
Use `AskUserQuestion` to collect:
```json
{
"questions": [
{
"question": "Quel est le code du projet ? (préfixe des containers Docker, ex: kotchi, myproject)",
"header": "Code projet",
"options": [
{"label": "Entrer le code", "description": "Je vais saisir le code du projet"}
],
"multiSelect": false
},
{
"question": "Quelle est l'URL/hostname de la VM du projet ? (ex: kotchi2, myproject.dev)",
"header": "URL VM",
"options": [
{"label": "Pas de VM", "description": "Développement local uniquement"},
{"label": "Entrer l'URL", "description": "Je vais saisir l'URL de la VM"}
],
"multiSelect": false
},
{
"question": "Le projet a-t-il un back office ?",
"header": "Back office",
"options": [
{"label": "Oui", "description": "Le projet a front + back office"},
{"label": "Non", "description": "Uniquement front office"}
],
"multiSelect": false
}
]
}
```
### 3. Create `.claude/project.json`
After collecting answers, create the file:
```json
{
"projectCode": "<user-provided-code>",
"projectUrl": "<user-provided-url-or-null>",
"hasBack": true|false,
"ssh": {
"host": "<projectUrl>",
"password": "<ask-if-needed>"
}
}
```
### 4. Verify required fields
| Field | Required | Description |
|-------|----------|-------------|
| `projectCode` | Yes | Docker container prefix |
| `projectUrl` | No | SSH hostname (null if local) |
| `hasBack` | Yes | Boolean for back office |
---
## Return Values
After verification, return the config for the calling agent:
```
CONFIG_OK:
- projectCode: <code>
- projectUrl: <url>
- hasBack: <true/false>
```
Or if user cancels:
```
CONFIG_CANCELLED: User declined to configure project
```
---
## Usage by Agents
Agents should call this skill at the start:
```markdown
## Step 0: Verify Configuration
Before starting, invoke the `symfony-sk:check-config` skill to ensure project is configured.
If config is missing, the skill will ask the user for information.
If user cancels, STOP and inform user that configuration is required.
```
---
## SSH Configuration (Optional)
If `projectUrl` is provided and SSH is needed:
1. Check if `.claude/project.json` has `ssh.password`
2. If missing, ask user for SSH password
3. Store in project.json (this file should be in .gitignore)
---
## Checklist
- [ ] `.claude/project.json` exists
- [ ] `projectCode` is set
- [ ] `hasBack` is set (boolean)
- [ ] If remote VM: `projectUrl` is set
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.