Porsche Design System

Audit Deprecations Skill

Table of Contents

Introduction
What It Audits
Installation
How to Use the Skill
Example Report
How to Act on the Report

Introduction#

The Audit Deprecations Skill scans a project for Porsche Design System APIs that are deprecated in the installed version and scheduled for removal in the next major release. It uses the version-exact deprecation index and includes the file, line and source evidence for every finding.

The audit is read-only: it writes two report files but never changes your code. Select your framework to adapt the skill name and examples on this page.

Invoking it looks like this, using your agent's skill selection syntax:

/pds-audit-deprecations-js Audit apps/checkout.

Aspect

Detail

Invocation

Explicit only. An agent never starts an audit on its own; you invoke pds-audit-deprecations-js yourself.

Dependencies

The Knowledge Skill (pds-knowledge-js), which supplies the deprecation index and the replacement references.

Reads

Project source, styles and Porsche Design System configuration, within the scope you give it. When you name none, that is the project root the agent runs in.

Writes

Nothing but its two report files, below .pds/audits/<runId>/.

Executes

Nothing. It does not install dependencies, build, test or start the application.

Invocation comes from the skill's frontmatter and is honored by your AI coding tool. The rest is guidance the skill gives an agent, not a permission your tool enforces.

What It Audits#

The audit checks:

Components, props, prop values, events and slots.

CSS custom properties, design tokens and styling integrations.

Stylesheet classes and icon names.

Usage passed through your own wrapper components.

Code quality, security, performance, accessibility and business logic are not in scope.

Installation#

The skill is bundled with the Porsche Design System npm packages. Follow the skill installation guide and install the required Knowledge Skill alongside it.

How to Use the Skill#

Scope each run to one application or package and name any excluded paths. Without a scope, the audit starts at the project root and may cover too much code to report reliably.

For the best results, start a fresh agent session, use a strong model and re-run any paths listed as partial in the report's coverage section.

/pds-audit-deprecations-js Audit apps/checkout. Exclude apps/checkout/e2e and any
generated files.

Example Report#

Each run writes two files into a fresh, timestamped run directory:

.pds/audits/2026-07-23T09-21-27Z/
├── pds-audit-deprecations-js.json
└── pds-audit-deprecations-js.md

The JSON validates against a published schema; the Markdown is the readable report. A shortened example:

# Porsche Design System deprecation audit (js) — 2026-07-23T09-21-27Z

- **PDS version audited:** `4.7.0`
- **Framework:** `js`
- **Project root:** `apps/checkout`
- **Result:** `completed`

…

## Summary

- **2** findings across **3** locations
- **1** manual follow-up

| Effort | Findings |
| --- | --- |
| `small` | 1 |
| `medium` | 1 |

| Confidence | Findings |
| --- | --- |
| `high` | 2 |

## Findings

Ordered cheapest first — effective effort ascending, then confidence, then occurrence count
descending, then rule id. This order is the recommended action plan.

### 1. Deprecated prop heading on p-accordion

- **Rule id:** `prop/p-accordion/heading`
- **Kind:** `prop`
- **Confidence:** `high`
- **Effort:** `small` (baseline)
- **Deprecation message:** Will be removed in the next major release. Use the `summary` slot instead.
- **Replacement:** `heading` → `summary slot`
- **Instruction:** Move the heading text into the `summary` slot instead of the `heading` prop.
- **Sources:**
  - `pds-knowledge-js/references/components/p-accordion/p-accordion.md` (PDS 4.7.0)
- **Locations (2):**
  - `src/components/faq-list.js:42` — `direct`
    ```
    accordion.heading = item.question;
    ```
  - `src/pages/specs.html:17` — `direct`
    ```
    <p-accordion heading="Technical data">
    ```

### 2. Deprecated component p-display

- **Rule id:** `component/p-display`
- **Kind:** `component`
- **Confidence:** `high`
- **Effort:** `medium` (baseline)
- **Deprecation message:** since v4.0.0, will be removed with next major release. Please use `p-heading` instead.
- **Replacement:** `p-display` → `p-heading`
- **Instruction:** Replace `p-display` with `p-heading`.
- **Sources:**
  - `pds-knowledge-js/references/components/p-display/p-display.md` (PDS 4.7.0)
- **Locations (1):**
  - `src/pages/home.html:28` — `direct`
    ```
    <p-display size="large">Taycan</p-display>
    ```

## Manual follow-ups

Detected but not statically resolvable. These are for a human to review — do not fix them
automatically.

### 1. p-text size

- **Reason:** The value arrives from a prop that no call site resolves, so whether it is a
  deprecated size cannot be determined statically.
- **Evidence (1):**
  - `src/components/price.js:19`
    ```
    text.size = options.size;
    ```

## How to act on this report

…

completed means the requested scope was checked. partial means the coverage section contains gaps that need a narrower follow-up run.

How to Act on the Report#

Work through findings in their listed order. Check manual follow-ups yourself and review medium confidence findings before changing code.

Apply fixes separately with the Knowledge Skill, which provides replacements for the installed version:

/pds-knowledge-js Apply the findings in
.pds/audits/2026-07-23T09-21-27Z/pds-audit-deprecations-js.md, in the order they are listed.
Use each finding's documented replacement, verify every usage against its quoted evidence before
changing it, and leave the manual follow-ups to me.

Audit the same scope again after applying fixes. Reports are not guaranteed to find every usage and only apply to the Porsche Design System version they name, so run a new audit after upgrading.