Imported from PietrangeloManco/PietrangeloManco (AGENTS.md). Install upstream with npx skills add PietrangeloManco/PietrangeloManco. Copyright stays with the author.

Profile repository instructions

Purpose

This is Pietrangelo Manco's GitHub profile repository. Manage it as a curated professional portfolio, not as a full repository index.

README Rules

• Keep the main README in English.
• Prioritize AI/ML, health tech, full-stack products, internal business platforms, and deployment-facing work.
• Public repositories can be linked when polished and portfolio-relevant.
• Private repositories may be mentioned high-level when they are important work.
• For private repositories, do not link source code or expose implementation details, credentials, datasets, model weights, business data, or internal operational data.
• Screenshots of private projects are allowed only when they come from a public logged-out surface or an unmistakably synthetic demo with permission-cleared branding.
• Frameworks and technologies used may be named.

Project Rules

• Do not expose Fylla or FraudDetection in the profile unless explicitly requested.
• Treat Prisma_IDE, Omnipredict_IDE, and MedLavDelta_IDE as private repositories: mention them high-level, do not link source code.
• Point Prisma and Omnipredict references to their public workflow notebooks stored in this profile repository.
• Treat CentroDeltaIDAB as My Centro Delta.
• Treat delta-biotech-pharma as Delta Biotech Pharma.
• Use https://mycentrodelta.com/ as the live product URL for My Centro Delta.
• Use https://deltabiotechpharma.it/ as the live product URL for Delta Biotech Pharma.
• Banknotes.eu can be shown as a private/high-level web project.
• Link private-work code only through fresh public companions with unrelated Git history and independently authored synthetic examples.
• Use healthcare-operations-platform-showcase for the generic operational-platform abstraction.
• Use wordpress-change-assurance-lab for the generic CMS assurance workflow.

Asset Rules

• Store profile screenshots under assets/screenshots/.
• Prefer local screenshot assets over external image URLs.
• Do not publish names, faces, dates, health readings, predictions, internal metrics, client records, private navigation structures, exact proprietary model features, or production configuration.
• Redaction alone is not sufficient when surrounding pixels still identify a person, measurement, account, organization, or workflow; replace the asset with synthetic content.
• Strip image metadata and inspect visible text at full resolution before publication.
• Avoid multi-column preview grids because GitHub tables do not stack on narrow screens; prefer single-column project sections.

Workflow

• Before updating, check the current GitHub repo list.
• Inspect candidate repo READMEs before adding profile entries.
• Keep edits scoped to portfolio presentation.
• Keep the README, local assets, notebooks, links, and these instructions consistent in the same change.
• Review git diff and git status before finishing.
• Unless the user opts out, commit and push only the scoped changes after validation; for this profile repository, the pushed README is the published surface and must be verified on GitHub.