POLYPOINT
- 22 skills
- 0 followers
- 2 hours ago last updated
- ▌ Pdx · polypoint bundleThis skill should be used when applying the PDX (POLYPOINT Design Experience) design system to Angular code — installing or using `@pdx/*` libraries, replacing Angular Material components with PDX equivalents, applying PDX design tokens or typography, building forms with `pp-form`, or auditing existing UI for PDX consistency. Triggers on phrases like "apply PDX styles", "use PDX libs", "use POLYPOINT components", "make it POLYPOINT-styled", "replace mat-button with pp-button", or "audit Material usage".
- ▌ Playwright API · polypoint bundleUse when the user wants to generate Playwright API-level corner case tests. Accepts an existing E2E test file or a free-form description, discovers API endpoints, then systematically generates corner case tests using APIRequestContext. No browser interaction.
- ▌ Playwright E2e · polypoint bundleUse when the user wants to create Playwright end-to-end tests from an annotated codegen recording. The user records a flow with `npx playwright codegen`, gives the test a descriptive name, adds `// assert that` comments, and this skill enriches it with resilient selectors via Chrome exploration and generates Page Object Model tests.
- ▌ Improve · polypointUse when the user wants to reflect on how the skills used in this session performed and file improvement plans — typically invoked as /improve right after a skill-driven task (e.g. /playwright-e2e … then /improve), or as /improve <skill-name> to focus on one skill. Uploads concrete, actionable plans as self-contained HTML pages to Whetstone for asynchronous human review.
- ▌ Research · polypoint bundleUse when the user wants to deeply understand a codebase topic, feature, module, or domain concept. Produces a structured research document with architecture diagrams, glossary, and actionable findings saved to the project's docs directory.
- ▌ Babysit Pr · polypoint bundleUse when asked to babysit, watch, monitor, or keep an eye on an Azure DevOps pull request for review comments and CI status — e.g. "babysit this PR for the next 30 minutes", "watch PR 12345 for comments and CI state", "handle the CodeRabbit findings as they come in", "kick CodeRabbit and CI off on my draft PR", "babysit it in a worktree so my checkout stays free". Runs a time-boxed watch via the az CLI, verifies each incoming finding against current code, fixes still-valid issues minimally, resolves bot threads, drafts replies to human threads for approval, and diagnoses failing builds.
- ▌ Dev Ticket · polypointUse when the user asks to actually work on a Jira ticket — do, fix, implement, take, start, resume, or finish it — in any language; never start coding a ticket without this skill, even if the request looks like a plain coding task. The signature is a ticket key like PROJECT-123 (any uppercase prefix — ABC-1234, PLAT-1290, PPCLOUD-14330) combined with intent to change code, however terse ("let's do X-123") or however much context surrounds it (bug details, urgency, PO assignment, screenshots, base branch). Runs the full lifecycle — fetch and analyze the ticket, reproduce, implement in an isolated git worktree, verify live with the user, commit, create the PR, shepherd it to merge. Also use for `/dev-ticket setup` (first-time project setup). Do NOT use when the user only wants information or Jira actions about a ticket (summarize, explain, estimate, status, transition, comment) or for coding tasks with no ticket involved.
- ▌ Pep Verify · polypoint bundleUse when driving or verifying things directly in PEP (POLYPOINT's Delphi/VCL personnel-planning Windows client) on a tenant box over RDP/SSH/WinRM — e.g. "verify yourself in PEP on ct-zinc-master", open the Stempeleditor, create a Zeitsumme/Block/Dienst, paint a shift onto the roster, rename a Dienst, read roster/GLAZ data, or change user permissions in UsrAdmin. Element-level automation (pywinauto over a loopback agent), not pixel clicking. Runs a preflight check and bootstraps the toolchain itself, then drives selector-based UI commands and flows. Requires the companion pep-driver toolchain.
- ▌ Redact Jira · polypointFetch a JIRA ticket's text and produce a privacy-safe version with all personal information redacted, before that text is used anywhere else in a review. Use at the start of a PR review, after the diff is available, to prepare the ticket description for comparison against the implementation.
- ▌ Review Open · polypointCross-cutting review step that runs after the focused steps. Connects the developer's already-accepted findings and surfaces concerns that fell between the dedicated steps (backwards-compat, operability, docs, config/migrations). Runs as a non-interactive sub-agent; the open-ended developer-directed part is handled by the orchestrator. Use as the last analysis step before drafting.
- ▌ Pp Pr Review · polypoint bundleUse when reviewing an Azure DevOps pull request through the complete POLYPOINT workflow: repository verification, JIRA PII redaction, parallel specialist reviews, developer-led triage, cross-cutting analysis, comment drafting, and explicitly approved posting. Trigger when the user supplies or refers to an Azure DevOps PR URL and asks for a PR or code review.
- ▌ Review Tests · polypointReview the tests in a pull request — useless/weak tests, missing coverage for changed behaviour, and whether integration tests are warranted. Runs as a non-interactive sub-agent producing a triageable findings report. Use as the test-focused judgment step of a PR review.
- ▌ Review Memory · polypointReview a pull request for memory problems — leaks, unbounded retention, and inefficient allocation — across Java/JVM (Spring, JPA/Hibernate), Node.js/TypeScript, and Angular (RxJS, DOM). Produces a structured, non-interactive findings report for the orchestrator to triage. Use as the memory-focused analysis step of a PR review.
- ▌ Review SQL Jpa · polypointReview a pull request for inefficient SQL and JPA/Hibernate usage — N+1 queries, missing pagination, over-fetching, bad transaction/fetch strategy, missing indexes. Stays in the data-access lane (general compute performance is a separate step). Produces a structured, non-interactive findings report for the orchestrator to triage.
- ▌ Review Security · polypointReview a pull request for security issues — injection, broken access control, auth/session flaws, secrets, XSS/CSRF/SSRF, insecure deserialization, misconfiguration — across Java/Spring, Node.js/TypeScript, and Angular. Grounded in OWASP. Produces a structured, non-interactive findings report for the orchestrator to triage.
- ▌ Zn2c Quick Win · polypointUse when implementing a Zn2C Quick-Win from the ZQW Jira board end-to-end, including Jira transitions, Confluence documentation, git worktree workflow, build validation, Azure DevOps PR creation, and review feedback handling.
- ▌ Draft Pr Comments · polypointTurn the developer's accepted review findings into well-formed, postable PR comments for Azure DevOps. Reads only the curated accepted-findings file. Runs as a non-interactive sub-agent producing the draft; the orchestrator presents it and applies edits. Use after triage, before the posting gate.
- ▌ Review Core Logic · polypointReview the core logic of a pull request against its ticket. Produces a plain-language summary, a ranked list of "review hot spots" (the most important logic, with clickable links to the code), a ticket-vs-implementation comparison, and triageable logic findings. Runs as a non-interactive sub-agent. Use as the first judgment step of a PR review.
- ▌ Review Guidelines · polypointReview a pull request against POLYPOINT's own documented Coding Guidelines — clean-code judgment rules and team-specific conventions (naming, structure, documentation) that generic linters and CodeRabbit don't know. Java/Spring backend and Angular/TS frontend. Produces a structured, non-interactive findings report for the orchestrator to triage.
- ▌ Review Performance · polypointReview a pull request for compute, concurrency, I/O, and rendering performance problems across Java/Spring, Node.js/TypeScript, and Angular. Excludes data-access/SQL-JPA and memory leaks (separate steps). Produces a structured, non-interactive findings report for the orchestrator to triage.
- ▌ Delphi To Angular · polypoint bundleUse when converting Delphi VCL views (.dfm/.pas) from the P2 codebase to Angular components. Handles forms, frames, data modules, grids, trees, tabs, and dialogs. Produces Angular components plus any needed store, service, mocks, routes, and tests matching the POLYPOINT saas repo stack. Extracts business rules from Delphi code, Oracle procedures, and DB constraints into rule cards that are enforced in the MSW handlers handed off to the backend team.
- ▌ Design Review For Developers · polypointPerforms a short, structured design review of design system components from a developer's perspective. Use whenever a developer wants a single component or small component group (button, input, card, dialog, etc.) checked against its Figma source — covering visual fidelity, states, accessibility, and implementation consistency. Not for full page or layout reviews.