@salesforce/templates 66.5.5 → 66.6.0

package/lib/templates/project/reactb2x/_p_/_m_/_w_/_a_/src/index.ts

@@ -1,120 +0,0 @@
-/**
- * Public API for the Global Search feature package.
- *
- * Design goals:
- * - Export **API services, hooks, types, schemas, and utilities** that customers can import from node_modules.
- * - Do **not** export UI components or feature constants (customers build their own UI).
- *
- * Source implementation lives under `src/features/global-search/**`.
- */
-
-// ---------------------------------------------------------------------------
-// API layer
-// ---------------------------------------------------------------------------
-
-export { objectInfoService } from "./features/global-search/api/objectInfoService";
-export {
-	objectDetailService,
-	extractFieldsFromLayout,
-} from "./features/global-search/api/objectDetailService";
-export type { RecordDetailResult } from "./features/global-search/api/objectDetailService";
-
-export {
-	getRecordsGraphQL,
-	getRecordByIdGraphQL,
-	buildGetRecordsQuery,
-	buildWhereFromCriteria,
-	buildOrderByFromSort,
-} from "./features/global-search/api/recordListGraphQLService";
-export type {
-	RecordListGraphQLResult,
-	RecordListGraphQLVariables,
-	RecordListGraphQLOptions,
-	GraphQLRecordNode,
-} from "./features/global-search/api/recordListGraphQLService";
-
-// ---------------------------------------------------------------------------
-// Hooks
-// ---------------------------------------------------------------------------
-
-export { useObjectInfoBatch } from "./features/global-search/hooks/useObjectInfoBatch";
-export {
-	useObjectListMetadata,
-	useObjectColumns,
-	useObjectFilters,
-} from "./features/global-search/hooks/useObjectSearchData";
-export { useRecordListGraphQL } from "./features/global-search/hooks/useRecordListGraphQL";
-export { useRecordDetailLayout } from "./features/global-search/hooks/useRecordDetailLayout";
-
-export type { ObjectListMetadata } from "./features/global-search/hooks/useObjectSearchData";
-
-export type {
-	UseRecordListGraphQLOptions,
-	UseRecordListGraphQLReturn,
-} from "./features/global-search/hooks/useRecordListGraphQL";
-
-export type {
-	UseRecordDetailLayoutParams,
-	UseRecordDetailLayoutReturn,
-} from "./features/global-search/hooks/useRecordDetailLayout";
-
-// ---------------------------------------------------------------------------
-// Types + Zod schemas (runtime validation)
-// ---------------------------------------------------------------------------
-
-export {
-	ColumnArraySchema,
-	SearchResultRecordArraySchema,
-	KeywordSearchResultSchema,
-	SearchResultsResponseSchema,
-} from "./features/global-search/types/search/searchResults";
-export type {
-	Column,
-	SearchResultRecord,
-	KeywordSearchResult,
-	SearchResultsResponse,
-} from "./features/global-search/types/search/searchResults";
-
-export {
-	FilterArraySchema,
-	FilterCriteriaArraySchema,
-	FILTER_OPERATORS,
-} from "./features/global-search/types/filters/filters";
-export type {
-	Filter,
-	FilterCriteria,
-	FilterOperator,
-	FiltersResponse,
-} from "./features/global-search/types/filters/filters";
-
-export type { PicklistValue } from "./features/global-search/types/filters/picklist";
-
-export type {
-	ObjectInfoBatchResponse,
-	ObjectInfoResult,
-} from "./features/global-search/types/objectInfo/objectInfo";
-
-export { LayoutResponseSchema } from "./features/global-search/types/recordDetail/recordDetail";
-export type { LayoutResponse } from "./features/global-search/types/recordDetail/recordDetail";
-
-// ---------------------------------------------------------------------------
-// Utilities
-// ---------------------------------------------------------------------------
-
-export { fetchAndValidate, safeEncodePath } from "./features/global-search/utils/apiUtils";
-export { debounce } from "./features/global-search/utils/debounce";
-export { createFiltersKey } from "./features/global-search/utils/cacheUtils";
-export {
-	calculateFieldsToFetch,
-	getSafeKey,
-	isValidSalesforceId,
-} from "./features/global-search/utils/recordUtils";
-export { parseFilterValue } from "./features/global-search/utils/filterUtils";
-export { sanitizeFilterValue } from "./features/global-search/utils/sanitizationUtils";
-export {
-	getGraphQLNodeValue,
-	getDisplayValueForDetailFieldFromNode,
-	getDisplayValueForLayoutItemFromNode,
-	getGraphQLRecordDisplayName,
-} from "./features/global-search/utils/graphQLNodeFieldUtils";
-export { graphQLNodeToSearchResultRecordData } from "./features/global-search/utils/graphQLRecordAdapter";

package/lib/templates/project/reactb2x/_p_/_m_/_w_/_a_/src/pages/Home.tsx

@@ -1,13 +0,0 @@
-import { GlobalSearchInput } from "../features/global-search/components/search/GlobalSearchInput";
-
-export default function Home() {
-	return (
-		<div className="max-w-7xl mx-auto px-4 sm:px-6 lg:px-8 py-12">
-			<div className="text-center">
-				<h1 className="text-4xl font-bold text-gray-900 mb-4">Home</h1>
-				<p className="text-lg text-gray-600 mb-8">Welcome to your React application.</p>
-			</div>
-			<GlobalSearchInput />
-		</div>
-	);
-}

package/lib/templates/project/reactb2x/_p_/_m_/_w_/_a_/tsconfig.tsbuildinfo

@@ -1 +0,0 @@
-{"root":["./src/app.tsx","./src/appLayout.tsx","./src/index.ts","./src/navigationMenu.tsx","./src/router-utils.tsx","./src/routes.tsx","./src/components/alerts/status-alert.tsx","./src/components/layouts/card-layout.tsx","./src/components/ui/alert.tsx","./src/components/ui/button.tsx","./src/components/ui/card.tsx","./src/components/ui/dialog.tsx","./src/components/ui/field.tsx","./src/components/ui/index.ts","./src/components/ui/input.tsx","./src/components/ui/label.tsx","./src/components/ui/pagination.tsx","./src/components/ui/select.tsx","./src/components/ui/separator.tsx","./src/components/ui/skeleton.tsx","./src/components/ui/spinner.tsx","./src/components/ui/table.tsx","./src/components/ui/tabs.tsx","./src/features/authentication/authHelpers.ts","./src/features/authentication/authenticationConfig.ts","./src/features/authentication/api/userProfileApi.ts","./src/features/authentication/context/AuthContext.tsx","./src/features/authentication/footers/footer-link.tsx","./src/features/authentication/forms/auth-form.tsx","./src/features/authentication/forms/submit-button.tsx","./src/features/authentication/hooks/form.tsx","./src/features/authentication/hooks/useCountdownTimer.ts","./src/features/authentication/hooks/useRetryWithBackoff.ts","./src/features/authentication/layout/card-skeleton.tsx","./src/features/authentication/layout/centered-page-layout.tsx","./src/features/authentication/layouts/AuthAppLayout.tsx","./src/features/authentication/layouts/authenticationRouteLayout.tsx","./src/features/authentication/layouts/privateRouteLayout.tsx","./src/features/authentication/pages/ChangePassword.tsx","./src/features/authentication/pages/ForgotPassword.tsx","./src/features/authentication/pages/Login.tsx","./src/features/authentication/pages/Profile.tsx","./src/features/authentication/pages/Register.tsx","./src/features/authentication/pages/ResetPassword.tsx","./src/features/authentication/sessionTimeout/SessionTimeoutValidator.tsx","./src/features/authentication/sessionTimeout/sessionTimeService.ts","./src/features/authentication/sessionTimeout/sessionTimeoutConfig.ts","./src/features/authentication/utils/helpers.ts","./src/features/global-search/constants.ts","./src/features/global-search/api/objectDetailService.ts","./src/features/global-search/api/objectInfoGraphQLService.ts","./src/features/global-search/api/objectInfoService.ts","./src/features/global-search/api/recordListGraphQLService.ts","./src/features/global-search/components/detail/DetailFields.tsx","./src/features/global-search/components/detail/DetailForm.tsx","./src/features/global-search/components/detail/DetailHeader.tsx","./src/features/global-search/components/detail/DetailLayoutSections.tsx","./src/features/global-search/components/detail/Section.tsx","./src/features/global-search/components/detail/SectionRow.tsx","./src/features/global-search/components/detail/UiApiDetailForm.tsx","./src/features/global-search/components/detail/formatted/FieldValueDisplay.tsx","./src/features/global-search/components/detail/formatted/FormattedAddress.tsx","./src/features/global-search/components/detail/formatted/FormattedEmail.tsx","./src/features/global-search/components/detail/formatted/FormattedPhone.tsx","./src/features/global-search/components/detail/formatted/FormattedText.tsx","./src/features/global-search/components/detail/formatted/FormattedUrl.tsx","./src/features/global-search/components/filters/FilterField.tsx","./src/features/global-search/components/filters/FilterInput.tsx","./src/features/global-search/components/filters/FilterSelect.tsx","./src/features/global-search/components/filters/FiltersPanel.tsx","./src/features/global-search/components/forms/filters-form.tsx","./src/features/global-search/components/forms/submit-button.tsx","./src/features/global-search/components/search/GlobalSearchInput.tsx","./src/features/global-search/components/search/ResultCardFields.tsx","./src/features/global-search/components/search/SearchHeader.tsx","./src/features/global-search/components/search/SearchPagination.tsx","./src/features/global-search/components/search/SearchResultCard.tsx","./src/features/global-search/components/search/SearchResultsPanel.tsx","./src/features/global-search/components/shared/LoadingFallback.tsx","./src/features/global-search/filters/FilterInput.tsx","./src/features/global-search/filters/FilterSelect.tsx","./src/features/global-search/hooks/form.tsx","./src/features/global-search/hooks/useObjectInfoBatch.ts","./src/features/global-search/hooks/useObjectSearchData.ts","./src/features/global-search/hooks/useRecordDetailLayout.ts","./src/features/global-search/hooks/useRecordListGraphQL.ts","./src/features/global-search/pages/DetailPage.tsx","./src/features/global-search/pages/GlobalSearch.tsx","./src/features/global-search/types/schema.d.ts","./src/features/global-search/types/filters/filters.ts","./src/features/global-search/types/filters/picklist.ts","./src/features/global-search/types/objectInfo/objectInfo.ts","./src/features/global-search/types/recordDetail/recordDetail.ts","./src/features/global-search/types/search/searchResults.ts","./src/features/global-search/utils/apiUtils.ts","./src/features/global-search/utils/cacheUtils.ts","./src/features/global-search/utils/debounce.ts","./src/features/global-search/utils/fieldUtils.ts","./src/features/global-search/utils/fieldValueExtractor.ts","./src/features/global-search/utils/filterUtils.ts","./src/features/global-search/utils/formDataTransformUtils.ts","./src/features/global-search/utils/formUtils.ts","./src/features/global-search/utils/graphQLNodeFieldUtils.ts","./src/features/global-search/utils/graphQLObjectInfoAdapter.ts","./src/features/global-search/utils/graphQLRecordAdapter.ts","./src/features/global-search/utils/layoutTransformUtils.ts","./src/features/global-search/utils/linkUtils.ts","./src/features/global-search/utils/paginationUtils.ts","./src/features/global-search/utils/recordUtils.ts","./src/features/global-search/utils/sanitizationUtils.ts","./src/lib/utils.ts","./src/pages/Home.tsx","./src/pages/NotFound.tsx","./vite-env.d.ts","./vitest-env.d.ts"],"version":"5.9.3"}

package/lib/templates/project/reactb2x/_r_/features/feature-graphql-graphql-data-access-rule.md

@@ -1,470 +0,0 @@
----
-paths:
-  - "**/*.ts"
-  - "**/*.tsx"
----
-
-# GraphQL Data Access
-
-Instructs agents to use the established GraphQL utilities for Salesforce data access.
-
-## TypeScript Types & Code Generation
-
-### Generated Types File
-
-Types are auto-generated at: `src/api/graphql-operations-types.ts`
-
-### Generation Command
-
-```bash
-npm run graphql:codegen
-```
-
-The codegen configuration is at `codegen.yml` and generates types from:
-
-- Schema: `schema.graphql` (project root)
-- Documents: `src/**/*.{graphql,ts,tsx}`
-
-### Type Naming Convention
-
-For a GraphQL operation named `GetHighRevenueAccounts`:
-
-- **Query/Mutation Response Type**: `GetHighRevenueAccountsQuery` or `GetHighRevenueAccountsMutation`
-- **Input Variables Type**: `GetHighRevenueAccountsQueryVariables` or `GetHighRevenueAccountsMutationVariables`
-
-## Core Types & Function Signatures
-
-### getDataSDK Function
-
-Available from `@salesforce/sdk-data`:
-
-```typescript
-import { getDataSDK } from "@salesforce/sdk-data";
-
-const data = await getDataSDK();
-const response = await data.graphql?.<ResponseType, VariablesType>(query, variables);
-```
-
-`getDataSDK()` returns a lazily-initialized `DataSDK` singleton. The `graphql` method uses optional chaining (`?.`) because not all surfaces support GraphQL.
-
-### gql Template Tag
-
-Also available from `@salesforce/sdk-data` for inline query definitions:
-
-```typescript
-import { gql } from "@salesforce/sdk-data";
-
-const MY_QUERY = gql`
-  query MyQuery {
-    uiapi {
-      ...
-    }
-  }
-`;
-```
-
-The `gql` tag is a template literal that allows defining GraphQL queries inline while maintaining syntax highlighting in most editors.
-
-### GraphQLResponse Shape
-
-`data.graphql?.()` returns `GraphQLResponse<T>`. Callers destructure `{ data, errors }` and handle errors themselves:
-
-```typescript
-interface GraphQLResponse<T> {
-  data: T;
-  errors?: Array<{
-    message: string;
-    locations?: Array<{ line: number; column: number }>;
-    path?: string[];
-  }>;
-}
-```
-
-### Handling Mixed Responses (Partial Success)
-
-GraphQL can return **both `data` and `errors`** in the same response (partial success). For example, some fields may resolve while others fail due to field-level security. Choose a strategy per use case:
-
-```typescript
-// Strategy A: Strict — treat any errors as failure (default for most queries)
-if (response?.errors?.length) {
-  throw new Error(response.errors.map((e) => e.message).join("; "));
-}
-const result = response?.data;
-
-// Strategy B: Tolerant — log errors but use partial data
-if (response?.errors?.length) {
-  console.warn("GraphQL partial errors:", response.errors);
-}
-const result = response?.data;
-
-// Strategy C: Discriminated — fail only when no data came back
-if (response?.errors?.length && !response?.data) {
-  throw new Error(response.errors.map((e) => e.message).join("; "));
-}
-if (response?.errors?.length) {
-  console.warn("Partial success with errors:", response.errors);
-}
-const result = response?.data;
-```
-
-**When to use each:**
-
-- **Strategy A** — Default. Use for queries where incomplete data would be misleading (e.g., financial summaries, approval workflows).
-- **Strategy B** — Use when partial data is still useful and the UI can degrade gracefully (e.g., dashboard tiles, optional fields).
-- **Strategy C** — Use for mutations where the operation may succeed but some return fields are inaccessible.
-
-For mutation-specific partial responses, see `docs/generate-mutation-query.md` which covers `PARTIAL` and `FAILED` status handling workflows.
-
-### NodeOfConnection Utility Type
-
-Extract the node type from a connection (edges/node pattern):
-
-```typescript
-import { type NodeOfConnection } from "@salesforce/sdk-data";
-
-// Extract Account node type from the query response
-type AccountNode = NodeOfConnection<GetHighRevenueAccountsQuery["uiapi"]["query"]["Account"]>;
-```
-
-### UIAPI Response Shape
-
-All Salesforce GraphQL record queries follow this structure (https://developer.salesforce.com/docs/platform/graphql/guide/query-record-objects.html):
-
-```typescript
-interface UIAPIQueryResponse {
-  uiapi: {
-    query: {
-      [ObjectName]: {
-        edges?: Array<{
-          node?: {
-            Id: string;
-            [FieldName]?: { value?: FieldType | null } | null;
-            // Reference fields include the related record
-            [ReferenceField]?: {
-              value?: string | null; // The ID
-              [RelatedField]?: { value?: RelatedType | null } | null;
-            } | null;
-          } | null;
-        } | null> | null;
-      } | null;
-    };
-  };
-}
-```
-
-## Required Workflow
-
-There are **two acceptable patterns** for defining GraphQL queries:
-
-### Pattern 1: External .graphql File (Recommended for complex queries)
-
-#### Step 1: Create .graphql File
-
-Store queries in `.graphql` files for codegen to process:
-
-```graphql
-# src/api/utils/query/myQuery.graphql
-query GetMyData($myVariable: String) {
-  uiapi {
-    query {
-      MyObject(first: 10, where: { Field: { eq: $myVariable } }) {
-        edges {
-          node {
-            Id
-            Name {
-              value
-            }
-          }
-        }
-      }
-    }
-  }
-}
-```
-
-#### Step 2: Run Code Generation
-
-```bash
-npm run graphql:codegen
-```
-
-This generates types in `graphql-operations-types.ts`:
-
-- `GetMyDataQuery` - response type
-- `GetMyDataQueryVariables` - variables type
-
-#### Step 3: Import and Use
-
-```typescript
-import { getDataSDK, type NodeOfConnection } from "@salesforce/sdk-data";
-import MY_QUERY from "./query/myQuery.graphql?raw";
-import type { GetMyDataQuery, GetMyDataQueryVariables } from "../graphql-operations-types";
-
-type MyNode = NodeOfConnection<GetMyDataQuery["uiapi"]["query"]["MyObject"]>;
-
-export async function getMyData(variables: GetMyDataQueryVariables): Promise<MyNode[]> {
-  const data = await getDataSDK();
-  const response = await data.graphql?.<GetMyDataQuery, GetMyDataQueryVariables>(
-    MY_QUERY,
-    variables,
-  );
-
-  if (response?.errors?.length) {
-    const errorMessages = response.errors.map((e) => e.message).join("; ");
-    throw new Error(`GraphQL Error: ${errorMessages}`);
-  }
-
-  return response?.data?.uiapi?.query?.MyObject?.edges?.map((edge) => edge?.node) || [];
-}
-```
-
-**Key imports for Pattern 1:**
-
-- `getDataSDK` - Get the DataSDK singleton
-- `NodeOfConnection` - Extract node types from connection responses
-- Query from `.graphql` file with `?raw` suffix
-- Generated types from `graphql-operations-types.ts`
-
-**Pattern 1 Benefits:**
-
-- Full codegen support with automatic type generation
-- Syntax highlighting and validation in `.graphql` files
-- Easier to share queries across multiple files/components
-- Better for complex queries with fragments and multiple variables
-- IDE support for GraphQL (autocomplete, validation)
-- Queries can be tested independently
-- Clear separation of concerns between query definition and usage
-
-**Pattern 1 Limitations:**
-
-- Requires separate file management
-- Extra step to run codegen after query changes
-- More boilerplate (file import with `?raw`, separate file to maintain)
-- Slight overhead for very simple queries
-- Need to navigate between files during development
-- Doesn't support dynamic queries (e.g., the set of fields changes based on runtime conditions and cannot be predetermined)
-
-### Pattern 2: Inline Query with gql Tag (Recommended for simple queries)
-
-For simpler queries without variables or when colocation is preferred:
-
-```typescript
-import { getDataSDK, gql } from "@salesforce/sdk-data";
-import { type CurrentUserQuery } from "../graphql-operations-types";
-
-const CURRENT_USER_QUERY = gql`
-  query CurrentUser {
-    uiapi {
-      currentUser {
-        Id
-        Name {
-          value
-        }
-      }
-    }
-  }
-`;
-
-interface User {
-  id: string;
-  name: string;
-}
-
-export async function getCurrentUser(): Promise<User | null> {
-  try {
-    const data = await getDataSDK();
-    const response = await data.graphql?.<CurrentUserQuery>(CURRENT_USER_QUERY);
-
-    if (response?.errors?.length) {
-      throw new Error(response.errors.map((e) => e.message).join("; "));
-    }
-
-    const userData = response?.data?.uiapi.currentUser;
-
-    if (!userData) {
-      throw new Error("No user data found");
-    }
-
-    return {
-      id: userData.Id,
-      name: userData.Name?.value || "User",
-    };
-  } catch (error) {
-    console.error("Error fetching user data:", error);
-    throw error;
-  }
-}
-```
-
-**Key imports for Pattern 2:**
-
-- `getDataSDK` - Get the DataSDK singleton
-- `gql` - Template tag for inline query definition
-- Generated types from `graphql-operations-types.ts`
-
-**Pattern 2 Benefits:**
-
-- Query is colocated with usage code
-- Supports dynamic queries (e.g., the set of fields changes based on runtime conditions and cannot be predetermined)
-- No separate file to maintain
-- Still gets type-checked against generated types
-- Simpler for straightforward queries
-
-**Pattern 2 Limitations:**
-
-- Inline queries without `gql` template tag are not processed by codegen
-- Must manually ensure query name matches generated types
-- Less suitable for complex queries with fragments
-
-## Conditional Field Selection with Directives
-
-For dynamic fieldsets with known fields that should be conditionally included, use GraphQL directives instead of building queries dynamically. This preserves type generation while allowing runtime control.
-
-### Directives
-
-- **`@include(if: $condition)`** - include field/fragment when `$condition` is `true`
-- **`@skip(if: $condition)`** - skip field/fragment when `$condition` is `true`
-
-### Example with Fragments
-
-```graphql
-query GetAccountDetails($id: ID!, $includeFinancials: Boolean!, $includeContacts: Boolean!) {
-  uiapi {
-    query {
-      Account(where: { Id: { eq: $id } }) {
-        edges {
-          node {
-            Id
-            Name {
-              value
-            }
-            ...FinancialFields @include(if: $includeFinancials)
-            ...ContactFields @include(if: $includeContacts)
-          }
-        }
-      }
-    }
-  }
-}
-
-fragment FinancialFields on Account {
-  AnnualRevenue {
-    value
-  }
-  NumberOfEmployees {
-    value
-  }
-}
-
-fragment ContactFields on Account {
-  Phone {
-    value
-  }
-  Website {
-    value
-  }
-}
-```
-
-### Usage
-
-```typescript
-import { getDataSDK } from "@salesforce/sdk-data";
-import QUERY from "./query/getAccountDetails.graphql?raw";
-import type {
-  GetAccountDetailsQuery,
-  GetAccountDetailsQueryVariables,
-} from "../graphql-operations-types";
-
-const data = await getDataSDK();
-const response = await data.graphql?.<GetAccountDetailsQuery, GetAccountDetailsQueryVariables>(
-  QUERY,
-  {
-    id: accountId,
-    includeFinancials: userWantsFinancials,
-    includeContacts: userWantsContacts,
-  },
-);
-```
-
-## Anti-Patterns (Not Recommended)
-
-### Direct API Calls
-
-```typescript
-// NOT RECOMMENDED: Direct axios/fetch calls for GraphQL
-const response = await axios.post("/graphql", { query });
-
-// PREFERRED: Use the DataSDK
-const data = await getDataSDK();
-const response = await data.graphql?.<ResponseType>(query, variables);
-```
-
-### Missing Type Definitions
-
-```typescript
-// NOT RECOMMENDED: Untyped GraphQL calls
-const data = await getDataSDK();
-await data.graphql?.(query);
-
-// PREFERRED: Provide response type
-const data = await getDataSDK();
-const response = await data.graphql?.<GetMyDataQuery>(query);
-```
-
-### Plain String Queries (Without gql Tag)
-
-```typescript
-// NOT RECOMMENDED: Plain string queries without gql tag
-const query = `query { ... }`;
-const data = await getDataSDK();
-await data.graphql?.(query);
-
-// PREFERRED: Use gql tag for inline queries
-const QUERY = gql`query { ... }`;
-const data = await getDataSDK();
-const response = await data.graphql?.<ResponseType>(QUERY);
-
-// OR: Use .graphql file for complex queries
-import QUERY from "./query/myQuery.graphql?raw";
-const data = await getDataSDK();
-const response = await data.graphql?.<ResponseType>(QUERY);
-```
-
-## Benefits of the DataSDK GraphQL API
-
-- Uses the DataSDK with proper authentication and CSRF token handling
-- Consistent typing with `GraphQLResponse<T>` interface
-- Optional chaining (`?.`) safely handles surfaces where GraphQL is unavailable
-- Callers get full `GraphQLResponse<T>` for flexible error handling
-
-## Quality Checklist
-
-Before completing GraphQL data access code:
-
-### For Pattern 1 (.graphql files):
-
-1. [ ] Create `.graphql` file for the query/mutation
-2. [ ] Run `npm run graphql:codegen` to generate types
-3. [ ] Import query with `?raw` suffix
-4. [ ] Import generated types from `graphql-operations-types.ts`
-5. [ ] Use `data.graphql?.<ResponseType>()` with proper generic
-6. [ ] Handle `response.errors` and destructure `response.data`
-7. [ ] Use `NodeOfConnection` for cleaner node types when needed
-8. [ ] Handle optional chaining for nested response data
-9. [ ] Follow the pattern in `accounts.ts`
-
-### For Pattern 2 (inline with gql):
-
-1. [ ] Define query using `gql` template tag
-2. [ ] Ensure query name matches generated types in `graphql-operations-types.ts`
-3. [ ] Import generated types for the query
-4. [ ] Use `data.graphql?.<ResponseType>()` with proper generic
-5. [ ] Handle `response.errors` and destructure `response.data`
-6. [ ] Handle optional chaining for nested response data
-7. [ ] Follow the pattern in `user.ts`
-
-### General:
-
-- [ ] Choose Pattern 1 for complex queries with variables, fragments, or when shared
-- [ ] Choose Pattern 2 for simple, colocated queries without complex requirements

package/lib/templates/project/reactb2x/_r_/features/feature-react-agentforce-conversation-client-embedded-agent-rule.md

@@ -1,18 +0,0 @@
----
-paths:
-  - "**/*.tsx"
-  - "**/components/**/*.ts"
----
-
-# Agentforce Conversation Client (standards)
-
-## DO NOT build a chat UI from scratch
-
-When the user asks for a chat UI, chat widget, chatbot, agent, or conversational interface — **always use the existing `AgentforceConversationClient` component** from `@salesforce/webapp-template-feature-react-agentforce-conversation-client-experimental`. Never generate a custom chat implementation, third-party chat library, WebSocket/REST chat, or direct calls to `embedAgentforceClient`.
-
-## Hard constraints
-
-- **`agentId` is required.** The component will not work without it. Always ask the user for their agent ID before generating code. Do not proceed without one.
-- **Use the React wrapper only.** Import `AgentforceConversationClient` from the package. Never call `embedAgentforceClient` directly.
-- **One instance per window.** Render in the app layout alongside `<Outlet />`, not on individual pages. The component is a singleton.
-- **No auth hard-coding.** The component resolves `salesforceOrigin` and `frontdoorUrl` automatically.

package/lib/templates/project/reactb2x/_r_/features/feature-react-chart-analytics-charts-rule.md

@@ -1,27 +0,0 @@
----
-paths:
-  - "**/*.tsx"
-  - "**/components/**/*.ts"
----
-
-# Analytics charts (standards)
-
-When adding or editing chart UI in this project, follow these conventions.
-
-## Components and library
-
-- Use the shared **AnalyticsChart** component (and **ChartContainer** when a framed block is needed). Do not use raw Recharts components for standard line or bar charts.
-- The project must have **recharts** installed (`npm install recharts`).
-
-## Data shape
-
-- **Time-series** (line): data must be an array of `{ x: string, y: number }`. Map raw fields (e.g. `date`, `value`) to these keys before passing to the chart.
-- **Categorical** (bar): data must be an array of `{ name: string, value: number }`. Map raw fields (e.g. `category`, `total`) accordingly.
-
-## Theming
-
-- Use only the **theme** prop on AnalyticsChart: `red` (decline/loss), `green` (growth/gain), `neutral` (default or mixed). Do not introduce ad-hoc color schemes for these semantics.
-
-## Placement
-
-- Render charts inside the existing application frame (e.g. main content or a route). Do not replace the full app shell with a single chart.