القائمة
SparkFabrik Drupal project container context. Use when running commands in local development environment, accessing Drupal from containers, or using fs-cli and make commands.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Invoke whenever the user is working with GitLab. Trigger on any of these signals: a URL containing "gitlab" (gitlab.com or any self-hosted instance like gitlab.sparkfabrik.com), a git remote pointing to GitLab (git@gitlab.com:... or https://gitlab...), the !N merge-request notation (!15, !42), or words like "merge request", "MR", "glab", or "gitlab". Handles issues, merge requests, CI/CD pipelines, releases, and reading files from GitLab repos. Always use glab—not WebFetch or curl—for any GitLab URL because GitLab requires authentication. Do not invoke for GitHub tasks (use the gh skill instead).
Invoke whenever the user is working with GitHub. Trigger on any of these signals: a URL containing "github.com" or a self-hosted GitHub Enterprise host, a git remote pointing to GitHub (git@github.com:... or https://github.com/...), the #N issue or PR notation (#15, #42), or words like "PR", "pull request", "gh", "GitHub issue", "GitHub Actions", "workflow run", "release", "gist", "review this PR", "merge this PR", "CI status", "checks", "fork", or "clone". Handles issues, pull requests, PR reviews and comments, GitHub Actions and CI runs, releases, gists, search, and reading files from GitHub repos. Always use gh, not WebFetch or curl, for any GitHub URL because gh handles authentication and returns structured data. This skill is the GitHub equivalent of glab for GitLab; if the project is on GitHub use this skill, and do not invoke it for GitLab tasks (use the glab skill instead).
Enforce SparkFabrik commit message and branch naming conventions including conventional commits, legacy format detection, issue references, branch prefixes, and the mandatory Assisted-by trailer. MUST be loaded before EVERY git commit, commit message preparation, MR/PR title creation, branch creation, or any commit-related operation. Use whenever the agent is about to run git commit, git checkout -b, git branch, write a commit message, create a branch, or prepare a merge request or pull request title. Also use when the user mentions "commit", "git commit", "conventional commit", "commit message", "refs #", "assisted-by", "commit convention", "branch name", "new branch", or "feature branch". Never create a commit or branch without consulting this skill first.
Create and manage Google Cloud Monitoring dashboards with Terraform (google_monitoring_dashboard) without perpetual plan drift. Use this skill whenever the user works with GCP monitoring dashboards in Terraform or any IaC context - creating a new dashboard, exporting a console dashboard to code, importing an existing dashboard into state, or debugging a terraform plan that keeps showing an in-place update on dashboard_json even right after apply. Trigger on mentions of google_monitoring_dashboard, dashboard_json, Cloud Monitoring / Stackdriver dashboards, dashboard drift, perma-diff, permadiff, "plan is never clean", mosaicLayout, or gcloud monitoring dashboards.
Browser automation with the playwright-cli tool. Use when the user needs to automate browser interactions, test web apps, take screenshots, fill forms, or extract data from pages. Trigger on: "playwright-cli", "playwright", "browser automation", "headless browser", "web scraping", "screenshot", "browser testing", "e2e test".
Configure, run, and troubleshoot Spark HTTP Proxy, the Traefik-based local development reverse proxy that gives Docker containers clean domain names (for example myapp.spark.loc) over HTTP and HTTPS. Use this skill whenever the user wants to expose a local container under a domain, edit a docker-compose service to add VIRTUAL_HOST/VIRTUAL_PORT or traefik.* labels, generate trusted local certificates with mkcert, set up .loc/.dev domain resolution, or debug why a container is not reachable through the proxy. Trigger on signals like VIRTUAL_HOST, VIRTUAL_PORT, spark-http-proxy, "http-proxy", *.spark.loc / *.loc / *.dev / .local dev domains, "my app is not routing locally", "expose this container", "localhost port chaos", mkcert / trusted local HTTPS, configure-dns, or a docker-compose.yml in a local project that should be reachable by name. This is for LOCAL DEVELOPMENT only; it is not for configuring a production Traefik deployment.
| name | sparkfabrik-drupal-containers |
| description | SparkFabrik Drupal project container context. Use when running commands in local development environment, accessing Drupal from containers, or using fs-cli and make commands. |
Reference for working with SparkFabrik Drupal projects in local development.
make targets or fs-cli commands# Open interactive shell in tools container
make drupal-cli
# All subsequent commands run inside the container
# Run a single command in tools container
docker compose run --rm -it drupal-tools <command>
# Examples
docker compose run --rm -it drupal-tools drush status
docker compose run --rm -it drupal-tools curl -sI http://drupal-nginx/
When running commands inside drupal-tools container, services are accessible by their container name.
To discover running services:
# List running services
docker compose ps
# Example: if you see "drupal-nginx" service, access it at http://drupal-nginx
Common pattern: Service names in docker compose ps correspond to their hostnames inside the container network (e.g., drupal-nginx → http://drupal-nginx).
Example:
# From inside container
curl -sI http://drupal-nginx/node/1
Use fs-cli to get external URLs:
# List all service URLs
fs-cli pkg:get-urls
# Get Drupal URL only
fs-cli pkg:get-urls | grep drupal-nginx | awk '{ print $2 }'
# Example output: https://drupal.projectname.sparkfabrik.loc:80
Example:
# From host machine
curl -sI https://drupal.projectname.sparkfabrik.loc/
Note: Replace projectname with your actual project name from the fs-cli pkg:get-urls output.
# List all available make targets
make help
From inside the container (make drupal-cli):
# Check status
drush status
# Clear cache
drush cr
# Run database updates
drush updb
# Export config
drush cex
# Import config
drush cim
| Task | From Container | From Host |
|---|---|---|
| Access Drupal | curl http://drupal-nginx/ | curl https://drupal.project.sparkfabrik.loc/ |
| Get URLs | N/A | fs-cli pkg:get-urls |
| Open shell | N/A | make drupal-cli |
| Run drush | drush <cmd> | docker compose run --rm drupal-tools drush <cmd> |