@mohammadhprp/system-prompt 0.10.1

package/framework/skills/brand-guidelines/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Anthropic, PBC.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/framework/skills/brand-guidelines/SKILL.md

@@ -0,0 +1,73 @@
+---
+name: brand-guidelines
+description: Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
+license: Complete terms in LICENSE.txt
+---
+
+# Anthropic Brand Styling
+
+## Overview
+
+To access Anthropic's official brand identity and style resources, use this skill.
+
+**Keywords**: branding, corporate identity, visual identity, post-processing, styling, brand colors, typography, Anthropic brand, visual formatting, visual design
+
+## Brand Guidelines
+
+### Colors
+
+**Main Colors:**
+
+- Dark: `#141413` - Primary text and dark backgrounds
+- Light: `#faf9f5` - Light backgrounds and text on dark
+- Mid Gray: `#b0aea5` - Secondary elements
+- Light Gray: `#e8e6dc` - Subtle backgrounds
+
+**Accent Colors:**
+
+- Orange: `#d97757` - Primary accent
+- Blue: `#6a9bcc` - Secondary accent
+- Green: `#788c5d` - Tertiary accent
+
+### Typography
+
+- **Headings**: Poppins (with Arial fallback)
+- **Body Text**: Lora (with Georgia fallback)
+- **Note**: Fonts should be pre-installed in your environment for best results
+
+## Features
+
+### Smart Font Application
+
+- Applies Poppins font to headings (24pt and larger)
+- Applies Lora font to body text
+- Automatically falls back to Arial/Georgia if custom fonts unavailable
+- Preserves readability across all systems
+
+### Text Styling
+
+- Headings (24pt+): Poppins font
+- Body text: Lora font
+- Smart color selection based on background
+- Preserves text hierarchy and formatting
+
+### Shape and Accent Colors
+
+- Non-text shapes use accent colors
+- Cycles through orange, blue, and green accents
+- Maintains visual interest while staying on-brand
+
+## Technical Details
+
+### Font Management
+
+- Uses system-installed Poppins and Lora fonts when available
+- Provides automatic fallback to Arial (headings) and Georgia (body)
+- No font installation required - works with existing system fonts
+- For best results, pre-install Poppins and Lora fonts in your environment
+
+### Color Application
+
+- Uses RGB color values for precise brand matching
+- Applied via python-pptx's RGBColor class
+- Maintains color fidelity across different systems

package/framework/skills/code-review/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: code-review
+description: Review backend changes for correctness, readability, maintainability, tests, performance, and security.
+version: 0.1.0
+---
+# Purpose
+Review backend changes for correctness, readability, maintainability, tests, performance, and security. This skill guides an AI agent to act with senior backend judgment: clarify the outcome, identify constraints, choose the least complex safe path, and make production impact visible.
+
+# When to Activate
+Use this skill when the task involves reviewing readability, correctness, naming, maintainability, testing, performance, security, or documentation. It is also useful when a request is vague, risky, touches production behavior, changes contracts, changes data, or needs a reviewable engineering plan. Do not activate it for trivial text edits unless the edit changes engineering guidance.
+
+# Principles
+- Correctness and data integrity come before speed of implementation.
+- Simplicity is a feature: fewer moving parts means fewer failure modes.
+- Existing contracts must remain compatible unless a breaking change is approved.
+- Every important decision should have a reason, an alternative considered, and an operational consequence.
+- Work should be testable, observable, deployable, and reversible.
+- Prefer explicit boundaries, clear names, and local reasoning over clever shared abstractions.
+- Security and privacy are design inputs, not final review steps.
+
+- Readability is production safety: reviewers must understand intent, invariants, and error paths.
+- Correctness includes edge cases, concurrency, compatibility, and failure behavior.
+- Naming should reveal business meaning rather than implementation mechanics.
+- Tests should prove behavior, not mirror implementation details.
+- Documentation is required when code alone cannot explain a decision or operational procedure.
+
+# Workflow
+1. Understand the change: what problem it solves, what behavior it modifies.
+2. Read the diff starting with contracts and interfaces before implementation.
+3. Check correctness: edge cases, concurrency, error handling, state transitions.
+4. Check maintainability: naming reflects business meaning, structure matches conventions, comments explain why not what.
+5. Check testing: do tests prove the behavior change? Are there missing edge cases or failure paths?
+6. Check performance: are there N+1 queries, unbounded loops, unnecessary allocations?
+7. Check security: are inputs validated, auth enforced, secrets exposed?
+8. Provide feedback: distinguish blockers from suggestions, explain reasoning.
+9. Summarize overall risk and readiness for production.
+
+# Rules
+- Never assume hidden requirements, traffic scale, compliance needs, or data retention rules.
+- Do not introduce new infrastructure unless the current requirement cannot be met safely without it.
+- Do not hide breaking changes in refactors.
+- Do not weaken authorization, validation, transaction safety, or error handling to make implementation easier.
+- Keep public contracts, migrations, and operational changes explicit in the deliverable.
+- Reference related standards: references/standards/naming.md, references/standards/testing.md.
+
+# Deliverables
+- Reviewed diff with per-section comments.
+- Blocker issues vs suggestions, clearly separated.
+- Overall risk assessment and readiness recommendation.
+- Summary of missing tests, docs, or operational signals.
+
+# Common Mistakes
+- Commenting on code style while missing correctness or security issues.
+- Requesting changes without explaining why they matter for production safety.
+- Approving changes that lack tests for failure paths and edge cases.
+- Ignoring operational concerns like logging, metrics, and error handling.
+- Treating reviewer feedback as blocking when it is a suggestion.
+
+# Failure Modes
+- A subtle correctness issue passes review because the reviewer focused on style.
+- A change is approved without test coverage for the main risk area.
+- Security vulnerabilities are missed because auth and input validation were not reviewed.
+- The review becomes a blocking gate rather than a quality collaboration.
+
+# Checklist
+- [ ] The change solves the stated problem without unnecessary scope.
+- [ ] Contracts and public APIs remain backward compatible or the breaking change is approved.
+- [ ] Edge cases, concurrency, and failure paths are handled.
+- [ ] Naming reveals business meaning, not implementation mechanics.
+- [ ] Tests exist for normal paths, edge cases, and failure modes.
+- [ ] No secrets, credentials, or sensitive data in the diff.
+- [ ] Logs, metrics, or traces are added for new operational concerns.

package/framework/skills/code-review/examples.md

@@ -0,0 +1,31 @@
+# Code Review Examples
+
+## Example 1: Missing Validation
+
+Review a PR that adds a POST /transfer endpoint with no input validation or auth. Good agent behavior:
+
+- Point out every input field (amount, source, target) should be validated for type, range, and format before reaching business logic.
+- Flag the missing authorization check: the caller must own the source account or have delegated permission.
+- Identify injection risk if any input is interpolated into SQL or rendered to HTML.
+- Recommend standard validation middleware and a consistent error shape rather than ad-hoc checks.
+- Request tests for invalid amounts, nonexistent accounts, and unauthenticated callers.
+
+## Example 2: N+1 Query
+
+Review a PR that fetches orders and then loops to load line items individually. Good agent behavior:
+
+- Identify the N+1 pattern: `SELECT * FROM orders` followed by `N` queries of `SELECT * FROM line_items WHERE order_id = ?`.
+- Recommend eager loading with a single batch query: `SELECT * FROM line_items WHERE order_id IN (?)`.
+- If using an ORM, point out the specific method that enables eager loading and note the performance difference.
+- Suggest pagination on orders to bound the total query volume.
+- Verify the fix with a test that asserts exactly 2 queries run (orders + line items) regardless of page size.
+
+## Example 3: Concurrency Bug
+
+Review a PR that updates account balances without locking. Good agent behavior:
+
+- Explain the race: two concurrent requests can read the same balance, subtract different amounts, and the second write clobbers the first.
+- Recommend optimistic locking with a version column: `UPDATE accounts SET balance = ?, version = version + 1 WHERE id = ? AND version = ?`.
+- If the ORM supports it, suggest using row-level locks (`SELECT FOR UPDATE`) inside a transaction.
+- Verify the update query itself is atomic: `UPDATE accounts SET balance = balance - ? WHERE id = ? AND balance >= ?` avoids the read-then-write gap.
+- Add a concurrency test that fires 10 parallel transfers and asserts the final balance matches the expected total.