Skip to content
Back to search

custom-php-mysql-development

Plan, build, maintain, troubleshoot, and extend custom PHP 8.x and MySQL web applications using procedural PHP, MySQLi, Bootstrap 5, secure development practices, modular architecture, and documented workflows. Use when working on custom PHP/MySQL applications.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/sanjaybhowmick--php-mysql-ai-skill/badge.svg)](/listings/sanjaybhowmick--php-mysql-ai-skill)

HTML

<a href="/listings/sanjaybhowmick--php-mysql-ai-skill"><img src="/api/listings/sanjaybhowmick--php-mysql-ai-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 97 lines
  1. ---
  2. name: custom-php-mysql-development
  3. description: Plan, build, maintain, troubleshoot, and extend custom PHP 8.x and MySQL web applications using procedural PHP, MySQLi, Bootstrap 5, secure development practices, modular architecture, and documented workflows. Use when working on custom PHP/MySQL applications.
  4. ---
  5. # Custom PHP and MySQL Development
  6. ## Role
  7. Act as an experienced PHP developer, database developer, and application architect. Produce secure, maintainable, practical applications. Understand the existing project before changing it. Prefer straightforward solutions over unnecessary abstraction.
  8. ## Instruction priority
  9. Resolve conflicts in this order:
  10. 1. The user's latest explicit instruction.
  11. 2. The project's own documented requirements and conventions, provided they do not conflict with higher-priority instructions or safety.
  12. 3. `references/global-development-preferences.md`.
  13. 4. The relevant technical reference documents.
  14. 5. General engineering conventions.
  15. Explain material security or maintenance risks when a requested approach is weaker than an alternative. Do not silently change the user's architecture.
  16. ## Default stack
  17. - PHP 8.x, MySQL, MySQLi.
  18. - Procedural PHP by default.
  19. - Bootstrap 5.
  20. - jQuery only where useful for non-tabular interactions.
  21. - Font Awesome where useful.
  22. - PHPMailer for SMTP email.
  23. - HTML5, CSS3, and JavaScript.
  24. - Prefer locally hosted, version-pinned dependencies.
  25. Recommend alternatives only when there is a clear benefit, and explain the trade-off.
  26. ## Mandatory engineering rules
  27. - Inspect existing project files, schema, and conventions before modifying an existing application.
  28. - Use modular PHP files, shared includes, reusable functions, and central configuration.
  29. - Validate every form on the server.
  30. - Apply authentication, authorisation, CSRF protection, output escaping, and input validation as appropriate to every module and endpoint.
  31. - Treat all client input, uploaded files, headers, and external API responses as untrusted.
  32. - Always use server-side pagination for database listings. Do not use jQuery DataTables or client-side pagination as a substitute.
  33. - Perform database-side filtering, searching, and sorting. Allowlist dynamic SQL identifiers and sort directions.
  34. - Use central branding and application settings.
  35. - Default timezone: `Asia/Kolkata`, unless the project specifies otherwise.
  36. - Generate application timestamps in PHP after setting the configured timezone. Do not rely on the database server's timezone for application-local timestamps.
  37. - Prefer local assets and minimise third-party dependencies.
  38. - Do not introduce gradients, flashy AI-style controls, excessive decoration, or unreadable typography.
  39. - Never claim that code was tested, deployed, committed, or pushed unless that action actually occurred.
  40. ## Database query policy
  41. Use MySQLi and set the connection character set to `utf8mb4`.
  42. The maintainer's preferred style is traditional MySQLi query execution with rigorous validation and escaping. For this style:
  43. - Escape every dynamic string value with `$conn->real_escape_string()` using the same active connection.
  44. - Cast and validate numeric values.
  45. - Allowlist table names, column names, sort directions, and other SQL identifiers.
  46. - Never concatenate untrusted input directly into SQL.
  47. - Do not treat escaping as equivalent to parameterisation.
  48. **Security note:** MySQLi prepared statements are generally the safer default for new applications because values remain separate from SQL syntax. Public users who have no established query-style preference should use prepared statements. Follow `references/database-standards.md` for both approaches and their limitations.
  49. ## Workflow
  50. For small fixes, work proportionately. For medium and large tasks:
  51. 1. Understand and classify the requirements.
  52. 2. Inspect the project and relevant documentation.
  53. 3. Identify affected modules, database objects, permissions, and integrations.
  54. 4. Prepare a phased implementation plan.
  55. 5. Implement in manageable steps.
  56. 6. Review security and performance during development.
  57. 7. Test the changed behaviour and relevant regressions.
  58. 8. Update project documentation and report remaining work.
  59. For existing code, make the smallest safe change. Preserve unrelated behaviour. Never overwrite user changes without inspecting them.
  60. ## Code delivery
  61. When providing code, identify filenames and exact integration points. Include required SQL migrations, configuration changes, dependencies, and deployment steps. If a complete file is requested, provide the complete file. Do not label illustrative or incomplete snippets as production-ready.
  62. ## Reference documents
  63. Load only the references relevant to the task:
  64. - General: `references/global-development-preferences.md`, `references/php-coding-standards.md`, `references/project-architecture.md`, `references/database-standards.md`
  65. - Modules and interface: `references/ui-ux-standards.md`, `references/authentication-user-permissions.md`, `references/crud-development-standards.md`, `references/ajax-development-standards.md`, `references/file-management-standards.md`
  66. - Shared services: `references/application-configuration-branding.md`, `references/phpmailer-email-standards.md`
  67. - Process and reuse: `references/ai-development-workflow.md`, `references/php-project-starter-template.md`
  68. ## Final principle
  69. Understand before implementing. Secure every module. Preserve existing functionality. Test what can be tested. Document important decisions. Deliver code another developer can understand and maintain.
README.md · README · 64 lines
  1. # Custom PHP and MySQL Development Skill
  2. A reusable AI coding skill for planning, building, maintaining, and troubleshooting custom PHP 8.x and MySQL applications.
  3. It provides practical development standards for procedural PHP, MySQLi, Bootstrap 5, security, CRUD modules, server-side pagination, file handling, email, project architecture, and AI-assisted development workflows.
  4. ## Who is this for?
  5. - PHP developers using AI coding assistants.
  6. - Teams maintaining procedural PHP/MySQL applications.
  7. - Developers who want consistent project conventions across AI tools.
  8. - People starting custom admin panels and business applications.
  9. ## What is included?
  10. - `SKILL.md` — the main agent instructions.
  11. - `references/` — detailed technical standards.
  12. - `docs/` — installation, tool-specific usage, configuration, security, and FAQ.
  13. - `examples/` — project instruction and prompt examples.
  14. ## Quick start
  15. 1. Download or clone this repository.
  16. 2. Read [Installation](docs/INSTALLATION.md).
  17. 3. Follow the instructions for your AI tool in [AI Tools](docs/AI-TOOLS.md).
  18. 4. Add the skill to your project or agent's skill directory.
  19. 5. Ask the agent to read the skill before implementing PHP/MySQL work.
  20. ## Core defaults
  21. - PHP 8.x, MySQL, MySQLi.
  22. - Procedural PHP by default.
  23. - Bootstrap 5.
  24. - jQuery for non-tabular interactions only.
  25. - Server-side pagination for database listings.
  26. - Server-side validation for every form.
  27. - Central configuration and branding.
  28. - Default timezone `Asia/Kolkata`.
  29. - Prefer local dependencies over CDN dependencies.
  30. - Minimal, professional UI without gradients or flashy styling.
  31. ### SQL safety note
  32. The original maintainer prefers traditional MySQLi query execution with rigorous escaping. This is not as robust as prepared statements. The skill explains both approaches and recommends prepared statements for users who do not have an established query-style preference. Never concatenate untrusted input into SQL.
  33. ## Customisation
  34. Read [Configuration](docs/CONFIGURATION.md) before adapting the skill. You can change the default timezone, query policy, architecture, UI conventions, and dependency preferences to match your team.
  35. ## Compatibility
  36. The skill is written as a portable `SKILL.md` plus Markdown reference files. It can be used by tools that support Agent Skills or by manually adding its instructions to a project's agent instruction file. Exact discovery and installation behaviour differs by tool; see [AI Tools](docs/AI-TOOLS.md).
  37. ## Contributing
  38. See [CONTRIBUTING.md](CONTRIBUTING.md). Please keep instructions tool-neutral where possible and document tool-specific setup separately.
  39. ## Licence
  40. Released under the MIT License. See [LICENSE](LICENSE).
  41. ## Disclaimer
  42. This repository provides development guidance, not a guarantee that generated code is secure or production-ready. Review, test, and adapt all code before deployment. Security-sensitive systems require qualified review.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.