메뉴
Drupal maintenance and support contract templates, task lists, SLA parameters, and handoff procedures. Use this skill when the user asks about Drupal maintenance contracts, support plans, SLA definitions, maintenance pricing, or needs guidance on dropping support/handoff procedures for a Drupal project.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Run the project markdownlint script in a Drupal project and fix the reported markdown violations. Use this skill whenever the user asks to run markdownlint, lint markdown, check the docs, or says "run scripts/markdownlint.sh and fix the errors".
Run PHPCS in a Drupal project and fix the reported coding standards violations. Use this skill whenever the user asks to run phpcs, check coding standards, fix code style errors, lint PHP/Drupal code, or says things like "run phpcs and fix the errors" or "clean up my coding standards".
Run PHPStan static analysis in a Drupal project and resolve the reported errors. Use this skill whenever the user asks to run phpstan, run static analysis, fix type errors, or says "run phpstan and fix the errors".
Run the custom PHPUnit test suite in a Drupal project and fix the reported failures and errors. Use this skill whenever the user asks to run phpunit, run the tests, run the custom testsuite, or says "run phpunit and fix the errors".
Estimate costs and timeline for Drupal projects using a structured breakdown of tasks, roles, content types, and development work. Use this skill when the user asks for a project quote, cost breakdown, timeline estimation, budget planning, or resource allocation for a Drupal website. Trigger for requests like "how much would this Drupal project cost", "estimate this project", "create a quote", "plan the budget", or any discussion about pricing/timeline for Drupal development.
Create a Drupal.org issue title and summary body that is ready to paste into the issue form. Use when the user asks to draft, improve, or rewrite an issue from a bug report, feature request, patch, MR, commit, or discussion. When the user says "issue title", "issue body", "issue summary", or similar.
| name | drupaltools-maintenance-contract |
| description | Drupal maintenance and support contract templates, task lists, SLA parameters, and handoff procedures. Use this skill when the user asks about Drupal maintenance contracts, support plans, SLA definitions, maintenance pricing, or needs guidance on dropping support/handoff procedures for a Drupal project. |
Templates and guidelines for Drupal maintenance and support contracts.
Source: https://raw.githubusercontent.com/theodorosploumis/notes/refs/heads/master/drupal/contract.md
This skill helps define, price, and manage Drupal maintenance contracts including SLAs, task lists, and project handoff procedures.
Before drafting a contract, assess these project factors:
Monthly hours needed based on project complexity:
| Project Type | Monthly Hours |
|---|---|
| Simple D8+ site, few modules | ~1 hour |
| Multisite (5 simple sites) | ~3 hours |
| Complex site, many modules/integrations | 6-10 hours |
| Simple Commerce site | ~6 hours |
| Large site with user accounts, 3rd party | 10+ hours |
Proposed schedule (from AdciSolutions):
| Frequency | Task |
|---|---|
| Monthly (1st Wednesday) | Minor Drupal version update (bug fixes) |
| Monthly (3rd Wednesday) | Check security releases in contrib modules |
| Monthly + 2 days post-deploy | Track errors (GA, logs, QA) |
| Quarterly | SEO audit |
| Semi-annually | Accessibility compliance check |
| Semi-annually | Google PageSpeed optimization |
| Semi-annually | Refactor frontend code |
| Annually | PHP version update |
| 2 weeks before expiry | SSL certificate renewal |
| Every update | Check custom code functionality |
| Every update | Update internal Support Sheet |
| Annually | Review/renew Support Contract terms |
When ending maintenance for a client:
.mycompany.domain subdomains (Cloudflare, etc.)known_hosts entries.git folders