epicenterhq/epicenter63 installs
single-or-array-pattern
Pattern for functions accepting a single item or array. Use when creating CRUD operations, batch processing APIs, or factories handling one or many inputs.
How do I install this agent skill?
npx skills add https://github.com/epicenterhq/epicenter --skill single-or-array-patternIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides architectural patterns and code examples for handling single or multiple inputs in TypeScript. It contains no executable scripts, external dependencies, or security risks.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerpass
1 file scanned · No issues
What does this agent skill do?
Single-or-Array Pattern
Accept both single items and arrays, normalize at the top, process uniformly.
Quick Reference
function create(itemOrItems: T | T[]): Promise<Result<void, E>> {
const items = Array.isArray(itemOrItems) ? itemOrItems : [itemOrItems];
// ... implementation works on items array
}
The Structure
- Accept
T | T[]as the parameter type - Normalize with
Array.isArray()at the top of the function - All logic works against the array : one code path
function createServer(clientOrClients: Client | Client[], options?: Options) {
const clients = Array.isArray(clientOrClients)
? clientOrClients
: [clientOrClients];
// All real logic here, working with the array
for (const client of clients) {
// ...
}
}
Naming Conventions
| Parameter | Normalized Variable |
|---|---|
recordingOrRecordings | recordings |
clientOrClients | clients |
itemOrItems | items |
paramsOrParamsArray | paramsArray |
When to Use
Good fit:
- CRUD operations (create, update, delete)
- Batch processing APIs
- Factory functions accepting dependencies
- Any "do this to one or many" scenario
Skip when:
- Single vs batch have different semantics
- Return types vary significantly
- Array version needs different options
Codebase Examples
Server Factory (packages/server/src/server.ts)
function createServer(
clientOrClients: AnyWorkspaceClient | AnyWorkspaceClient[],
options?: ServerOptions,
) {
const clients = Array.isArray(clientOrClients)
? clientOrClients
: [clientOrClients];
// All server setup logic directly here
const workspaces: Record<string, AnyWorkspaceClient> = {};
for (const client of clients) {
workspaces[client.id] = client;
}
// ...
}
Service Method
delete: async (recordingOrRecordings) => {
const recordings = Array.isArray(recordingOrRecordings)
? recordingOrRecordings
: [recordingOrRecordings];
const ids = recordings.map((r) => r.id);
return tryAsync({
try: () => store.bulkDelete(ids),
catch: (error) => RecordingStoreError.MutationFailed({ cause: error }),
});
},
RPC Mutation
export const recordingKeys = defineKeys({
delete: ['recordings', 'delete'],
});
type DeleteRecordingsInput = Recording | Recording[];
export const recordings = {
delete: defineMutation({
mutationKey: recordingKeys.delete,
mutationFn: async (recordings: DeleteRecordingsInput) => {
const recordingsArray = Array.isArray(recordings)
? recordings
: [recordings];
for (const recording of recordingsArray) {
services.blobs.audio.revokePlaybackUrl(recording.id);
}
const { error } = await services.recordings.delete(recordingsArray);
if (error) return Err(error);
return Ok(undefined);
},
}),
};
Anti-Patterns
Don't: Separate functions for single vs array
// Harder to maintain, users must remember two APIs
function createRecording(recording: Recording): Promise<...>;
function createRecordings(recordings: Recording[]): Promise<...>;
Don't: Force arrays everywhere
// Awkward for single items
createRecordings([recording]); // Ugly
Don't: Duplicate logic in overloads
// BAD: Logic duplicated
function create(item: T) {
return db.insert(item); // Duplicated
}
function create(items: T[]) {
return db.bulkInsert(items); // Different code path
}
// GOOD: Single implementation
function create(itemOrItems: T | T[]) {
const items = Array.isArray(itemOrItems) ? itemOrItems : [itemOrItems];
return db.bulkInsert(items); // One code path
}
References
- Full article : detailed explanation with more examples
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/epicenterhq/epicenter/single-or-array-pattern">View single-or-array-pattern on skillZs</a>